$ the-wire · showcase
VITEPRESS LOCKS IN METACHUNK BY DEFAULT
By RepoJournal · Filed · About Vue.js · Composed from the cited sources · methodology
1 person shipped this
VitePress is removing the metaChunk configuration option entirely, forcing all sites onto the optimization that was previously optional.
VitePress shipped a breaking change that enables metaChunk by default and removes the ability to disable it [1]. This closes out months of discussion about whether the feature should be the standard behavior [1]. The change consolidates build output into fewer chunks, which improves initial load times for most sites but means you can't opt out if your build process depends on the old chunking strategy. If you're running custom chunk splitting logic or have deployment pipelines that expect specific chunk patterns, test this against your builds before upgrading.
Action items
- → Test VitePress upgrade in staging if you have custom chunk splitting vuejs/vitepress [plan]
- → Review metaChunk impact on your static bundle size vuejs/vitepress [monitor]
References
- [1] feat: enable metaChunk by default ↗ vuejs/vitepress
