The Wire ยท Showcase
VITEPRESS FIXES ASSET INVALIDATION BUG THAT BREAKS FRAMEWORK CHUNK CACHING
By RepoJournal ยท Filed ยท About Vue.js
VitePress stopped unnecessarily invalidating your framework chunk every time a new asset lands, cutting rebuild times on asset-heavy sites.
The fix [1] tackles a real problem: adding a single image or stylesheet was nuking the entire framework bundle from cache, forcing a full rebuild on every deploy. That's brutal for large sites where the framework chunk is your biggest asset. The team also cleaned up the type layer [2] to keep the codebase maintainable as these optimizations stack up. This is exactly the kind of invisible performance win that compounds across thousands of sites. If you're building with VitePress and noticed slow rebuilds after adding assets, this lands today.
Action items
- โ Pull the latest VitePress to get the asset caching fix vuejs/vitepress [plan]
References
- [1] fix: don't invalidate framework chunk when a new asset is added vuejs/vitepress
- [2] refactor: clean up types vuejs/vitepress
FAQ
- What changed in Vue.js on July 5, 2026?
- VitePress stopped unnecessarily invalidating your framework chunk every time a new asset lands, cutting rebuild times on asset-heavy sites.
- What should Vue.js teams do about it?
- Pull the latest VitePress to get the asset caching fix
- Which Vue.js repositories shipped on July 5, 2026?
- vuejs/vitepress