@next/swc-wasm-web
16.4.6 · 9 Nov 20268.3k / weekRepositoryHomepagenpmAtom feed
Upgrading @next/swc-wasm-web From 15.4.8 to 15.5.29
22 releases in betweenevery note read
- 8
- changes to make
- 0
- advisories fixed
- 48
- new
- 125
- fixes
Before you upgrade
Tick each one off as you go- Breaking15.5.0
- Breaking15.5.0
- Breaking15.5.0
- Breaking15.5.0
- Breaking15.5.0
- Deprecated15.5.5
- Deprecated15.5.0
- Deprecated15.5.0
Security
- 15.5.29
- 15.5.29
- 15.5.29
- 15.5.28
- 15.5.28
- 15.5.27
- 15.5.27
- 15.5.27
- 15.5.26
This release contains additional security hardening for
next/og. - 15.5.24
Release by release
- Security
- Security
- Security
- Security
- Security
- Security
- Security
- Security
- Security
This release contains additional security hardening for
next/og.
- Security
15.5.25nothing new or fixed in the note
15.5.22 – 15.5.232 releases, nothing new or fixed in the notes
- Security
- Security
- Security
- Security
105 other lines we could not sort, mostly version bumps
- 15.5.23
Port ReplyServer traversal guards to FlightClient @eps1lon
- 15.5.22
Reject TypeScript >= 7.0 with an actionable error
- 15.5.5
Split code-frame into separate compiled package
- 15.5.4
Improve handling of symlink resolution errors in track_glob and read_glob
- 15.5.4
Turbopack: Throw large static metadata error earlier
- 15.5.4
Turbopack: Flush Node.js worker IPC on error
- 15.5.2
Add ?dpl to fonts in /_next/static/media
- 15.5.0
Use and enforce exhaustive switch statements for work unit store
- 15.5.0
Use RSC dynamicness to control partial vs complete PPR result
- 15.5.0
Turbopack: content-hash PageLoaderAsset
147 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.