@nuxt/rspack-builder
4.6.4 · 2 Nov 2026MIT590 / weekRepositoryHomepagenpmAtom feed
Upgrading @nuxt/rspack-builder From 4.0.3 to 4.1.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
Security
2 advisories still affect 4.1.0
- Nuxt: Dev server exposes built source over LAN to malicious sites (incomplete fix for GHSA-4gf7-ff8x-hq99)moderate · GHSA-6m52-m754-pw2g
- @nuxt/webpack-builder and @nuxt/rspack-builder dev server same-origin check bypassed when Sec-Fetch-Site, Origin, and Referer are all absent (incomplete fix for GHSA-6m52-m754-pw2g)moderate · GHSA-x6qj-4h56-5rj5
Upgrading to 4.4.7 clears them.
Release by release
- New
A component is changed slightly - the hash of its JS chunk changes
- New
The page which uses the component has to be updated to reference the new file name
- New
The entry now has its hash changed because it dynamically imports the page
- New
every other file which imports the entry has its hash changed because the entry file name is changed
- New
44 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.