@next/bundle-analyzer
16.4.6 · 9 Nov 2026MIT6.4M / weekRepositoryHomepagenpmAtom feed
Upgrading @next/bundle-analyzer From 9.0.2 to 9.5.5
35 releases in betweenevery note read
Reading releases, release notes and advisories…
- 22
- changes to make
- 0
- advisories fixed
- 394
- new
- 1442
- fixes
Before you upgrade
Tick each one off as you go- Breaking9.5.4
- Breaking9.5.0
- Breaking9.5.0
- Breaking9.4.0
- Breaking9.3.6
- Breaking9.3.5
- Breaking9.3.0
- Breaking9.2.0
- Breaking9.1.7
- Breaking9.1.5
Security
- 9.5.4
A security team from one of our partners noticed an issue in Next.js that allowed for open redirects to occur.
- 9.5.4
Specially encoded paths could be used with the trailing slash redirect to allow an open redirect to occur to an external site.
- 9.5.4
We've landed a patch that ensures encoding is handled properly for these types of redirects so the open redirect can no longer occur.
- 9.5.4
Regression tests for this attack were added to the security integration test suite.
- 9.3.2
Regression tests for this attack were added to the security integration test suite.
Release by release
- Fixed
Handle css-loader file resolving change
- Fixed
- Security
A security team from one of our partners noticed an issue in Next.js that allowed for open redirects to occur.
- Security
Specially encoded paths could be used with the trailing slash redirect to allow an open redirect to occur to an external site.
- Security
We've landed a patch that ensures encoding is handled properly for these types of redirects so the open redirect can no longer occur.
- Security
Regression tests for this attack were added to the security integration test suite.
- Security
- New
Add codemod documentation
- New
Add initial handling for dynamic route href resolving and rewrites on the client
- New
Allow React experimental version without warning
- New
Add experimental webpack 5 cache option
- New
- New
Add additional pageProps check
- New
Support persisting the dev cache buster
- New
Add missing nomodule polyfills and suggest using features only up to ES2019 for browser compatibility
- New
Add support for
fallback: 'blocking'
- New
- New
Add polyfill for process and Buffer in webpack 5
- New
Add better typing for redirect
- New
Add release hook to format the changelog by labels
- Fixed
UnhandledPromiseRejectionWarning when unknown flag provided for cli commands
- New
- Breaking
Remove granularChunks experimental option as it was launched
- Breaking
Remove deprecated webpack plugin in favor of the option
- Deprecated
Deprecate with-sentry in favor of with-sentry-simple
- New
Use buildManifest to load page JS
- Breaking
- New
Add note about GS(S)P imports
- Fixed
Do not import from
fs-extra
- New
- New
Better formatted Sass errors
- New
Add support for sass-loader prependData option
- New
Make page path case sensitive in dev
- New
cli: Use default template when GH is offline
- New
111 other lines we could not sort, mostly version bumps
- 9.5.5
Update to have default locale matched on root
- 9.5.4
We have released patch versions for both the stable and canary channels of Next.js.
- 9.5.4
To upgrade run
npm install next@latest --save - 9.5.4
Affected: Users of Next.js between 9.5.0 and 9.5.3
- 9.5.4
Not affected: Deployments on Vercel (vercel.com) are not affected
- 9.5.4
Not affected: Deployments using
next export - 9.5.4
We have notified known Next.js users in advance of this publication.
- 9.5.4
A public CVE was released.
- 9.5.4
If you want to stay on top of our security related news impacting Next.js or other Vercel projects, please join this mailing list.
- 9.5.4
We encourage responsible disclosure of future issues. Please email us at security@vercel.com. We are actively monitoring this mailbox.
541 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.