Enable Rollups output.experimentalDeepDynamicChunkOptimization #2013
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#2013
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This should reduce the currently exessive amount of chunks.
https://github.com/rollup/rollup/pull/4837
Sounds like a good idea. Can we test this locally first?
Should be possible by comparing the amount of chunks that got put out.
Now I'm really unsure if this makes sense:
Before
With
experimentalDeepDynamicChunkOptimization: trueThat got me thinking. I looked up the chunk options in rollup and found an example configuration function at the end of the manualChunks option explanation.
With rollup example
manualChunksconfigurationThat actually seems better, mostly because the index chunk is much smaller which should improve initial loading! But chunks from vendors are all integrated. I'm unsure how much sense that makes.
Comparing this with Vites integrated
SplitVendorChunkconfigurationTo be honest I don't care for people that don't use http2 at this point, meaning we can and should use as many files as make sense (more than with old http).
How many that is I have no clue :D
You mean there's no vendor chunk with all dependencies?
Yes. See that log when expand the
<details>.I mean it probably does not hurt, question is where these dependencies go - in the component chunks where they are used? Does this create duplicates when the same dependency is used in multiple places?
If I understood this correctly it might be depending on the case. Meaning: the total filesize of the output might be larger but: it won't need to load some chunks only because a small dependency from it is needed.
Rollup improved its chunking strategy so this is obsolete now.
See: https://github.com/rollup/rollup/pull/4862