Packages

@next/bundle-analyzer

16.4.6 · 9 Nov 2026MIT6.4M / weekRepositoryHomepagenpmAtom feed

Upgrading @next/bundle-analyzer From 11.0.1 to 11.1.4

5 releases in betweennotes for 4

Reading releases, release notes and advisories…

Other targets from 11.0.1Latest16.4.6
?
changes to make
0
advisories fixed
74+
new
64+
fixes

Counted from 4 of 5 release notes. Advisories are counted from the advisory database, in full.

Security

  • A security team from one of our partners noticed an issue in Next.js that allowed for an open redirect to occur.

    11.1.0
  • Specially encoded paths could be used when pages/_error.js was statically generated allowing an open redirect to occur to an external site.

    11.1.0
  • We've landed a patch that ensures path parsing is handled properly for these paths so that the open redirect can no longer occur.

    11.1.0
  • Regression tests for this attack were added to the security integration test suite

    11.1.0

Release by release

  1. 11.1.3 – 11.1.42 releases, nothing new or fixed; 1 without a note

  2. 11.1.2

    31 Aug 20211 fix
    • Fixed

      Ensure custom app regex is correct for Windows

  3. 11.1.1

    30 Aug 202119 new · 22 fixes
    • New

      Add missing fields to NextConfig type

    • New

      Add support for dynamic HTML

    • New

      Support suspense in next dynamic

    • New

      Add proper error when failing to load next.config.js

  4. 11.1.0

    Security fix11 Aug 202155 new · 41 fixes
    • Security

      A security team from one of our partners noticed an issue in Next.js that allowed for an open redirect to occur.

    • Security

      Specially encoded paths could be used when pages/_error.js was statically generated allowing an open redirect to occur to an external site.

    • Security

      We've landed a patch that ensures path parsing is handled properly for these paths so that the open redirect can no longer occur.

    • Security

      Regression tests for this attack were added to the security integration test suite

92 other lines we could not sort, mostly version bumps
  • getServerSideProps should support props value as Promise

    11.1.2
  • Next.js swc publish flow

    11.1.1
  • Use a shared worker pool for collecting page data and static page generation

    11.1.1
  • Use @next scope for native packages

    11.1.1
  • Clean up Document in preparation for streaming

    11.1.1
  • Render as a concatenation of streams

    11.1.1
  • Bypass webpack compilation for precompiled @next/polyfills-nomodule

    11.1.1
  • Remove duplicate doctypes

    11.1.1
  • Update to latest babel versions

    11.1.1
  • Improve jaeger traces

    11.1.1

193 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.