[Snyk] Upgrade next from 16.0.10 to 16.1.1 #90
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade next from 16.0.10 to 16.1.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 64 versions ahead of your current version.
The recommended version was released a month ago.
Release notes
Package name: next
Core Changes
Misc Changes
Credits
Huge thanks to @ bgw, @ sokra, and @ naveenkarmegam for helping!
Misc Changes
Credits
Huge thanks to @ ztanner and @ icyJoseph for helping!
Misc Changes
Optimizing Package Bundlingto include new Bundle Analyzer: #87246livenessof exports based on assignment analysis (#82802)"": #87214Credits
Huge thanks to @ sokra, @ Juneezee, @ delbaoliveira, @ icyJoseph, @ wbinnssmith, @ ztanner, and @ lukesandberg for helping!
Core Changes
f93b9fd4-20251217to65eec428-20251218: #87323Misc Changes
Credits
Huge thanks to @ icyJoseph for helping!
Tip
Check out our Next v16.1 Blog Post to learn more about this release.
Core Changes
next dev --inspect: #85037b4455a6e-20251027to4f931700-20251029: #85518cacheLifetypes out of the webpack plugin and into the dev bundler directly: #85539'use cache'in page/layout component: #855194f931700-20251029to561ee24d-20251101: #85670'next'plugin: #85749561ee24d-20251101to67f7d47a-20251103: #8576267f7d47a-20251103tof646e8ff-20251104: #85772f646e8ff-20251104todd048c3b-20251105: #85819dd048c3b-20251105tofa50caf5-20251107: #85906'use cache'call stacks: #85966fa50caf5-20251107to52684925-20251110: #8598052684925-20251110to93fc5740-20251113: #8610393fc5740-20251113tofb2177c1-20251114: #86155next devis already running: #86083next analyze: a built-in bundle analyzer for Turbopack: #85915experimental.turbopackClient/ServerSideNestedAsyncChunking: #85827next upgrade: #86120fb2177c1-20251114to0972e239-20251118: #86263next analyze: Make ipv6 server links valid and normalize localhost: #86219detailfield of issues: #86518npxifyarn dlxis not available: #86384'use cache'module to a cache function: #86014setReferenceManifestsSingletoncall: #86574'use cache'runtime errors in production: #865008ac5f4eb-20251119tofd524fe0-20251121: #86473