152 wires and counting

$ follow Vue.js

Keep up with Vue.js in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-07-05
stories 2

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

VITEPRESS FIXES ASSET INVALIDATION BUG THAT BREAKS FRAMEWORK CHUNK CACHING

By RepoJournal · Filed · About Vue.js · Composed from the cited sources · methodology

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.

Quick answers

What shipped 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. In total, 2 commits landed.
What were the notable Vue.js updates?
fix: don't invalidate framework chunk when a new asset is added and refactor: clean up types.