@next/eslint-plugin-next
16.4.6 · 9 Nov 2026MIT57.3M / weekRepositoryHomepagenpmAtom feed
Upgrading @next/eslint-plugin-next From 11.0.0 to 11.1.4
6 releases in betweennotes for 5
Reading releases, release notes and advisories…
- 1+
- change to make
- 0
- advisories fixed
- 77+
- new
- 76+
- fixes
Counted from 5 of 6 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Breaking11.0.1
Security
- 11.1.0
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.jswas 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
Release by release
11.1.3 – 11.1.42 releases, nothing new or fixed; 1 without a note
- Fixed
Ensure custom app regex is correct for Windows
- Fixed
- New
Add missing fields to
NextConfigtype - New
Add support for dynamic HTML
- New
Support suspense in next dynamic
- New
Add proper error when failing to load next.config.js
- New
- 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.jswas 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
- Security
- Breaking
Follow the breaking change of jest-config
- New
Adds
--quietflag, TypeScript resolver and bug fixes - New
Add runtime to hotUpdateMainFilename
- New
Add check for startLatency in fast refresh
- Breaking
97 other lines we could not sort, mostly version bumps
- 11.1.2
getServerSideProps should support props value as Promise
- 11.1.1
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
Documentin 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
234 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.