@next/eslint-plugin-next
16.4.6 · 9 Nov 2026MIT57.3M / weekRepositoryHomepagenpmAtom feed
Upgrading @next/eslint-plugin-next From 12.0.8 to 12.0.9
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 3
- changes to make
- 0
- advisories fixed
- 5
- new
- 10
- fixes
Before you upgrade
Tick each one off as you go- Breaking12.0.9
- Breaking12.0.9
- Deprecated12.0.9
Release by release
- Breaking
Remove node fetch polyfill from base server
- Breaking
Removed backticks on data fetching api titles
- Deprecated
errors/no-cache:
netlify-plugin-cache-nextjshas been deprecated - New
Implement abstract methods to get manifest files in the base server
- Breaking
29 other lines we could not sort, mostly version bumps
- 12.0.9
We have released patch versions for both the stable and canary channels of Next.js.
- 12.0.9
To upgrade run
npm install next@latest --save - 12.0.9
Affected: All of the following must be true to be affected by this CVE
- 12.0.9
Deployments on Vercel (vercel.com) are not affected along with similar environments where invalid requests are filtered before reaching Next.js.
- 12.0.9
A public CVE was released.
- 12.0.9
We encourage responsible disclosure of future reports. Please email us at
security@vercel.com. We are actively monitoring this mailbox. - 12.0.9
middlewares: Limit
process.envto inferred usage - 12.0.9
Update webpack
- 12.0.9
Abstract out native filesystem usage from the base server
- 12.0.9
Use text data url instead of base64 for shorter encoding
43 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.