The React Framework
Published Node.js and peer-dependency requirements.
| Requirement | From12.0.4 on npm (opens in a new tab) | To12.0.5 on npm (opens in a new tab) |
|---|---|---|
react | ^17.0.2 || ^18.0.0Required peer | ^17.0.2 || ^18.0.0-0Required peer |
react-dom | ^17.0.2 || ^18.0.0Required peer | ^17.0.2 || ^18.0.0-0Required peer |
3 Dec 2021 · Newest first
Last checked
Checking sources…
Showing 1 of 1 releases. Full release notes.
Signals highlight changes worth reviewing. They cannot determine whether your application is affected.
Remove outdated comment about string children being deprecated in
next/link: #30606
Fix with-mongo example by removing deprecated function: #30675
We've landed a patch that ensures this is handled properly so the
unhandledPromiseRejectionissue no longer occurs.
This upgrade is completely backward-compatible and recommended for all users on versions below 12.0.5. A backport of the patch to Next.js 11 is available as 11.1.3.
When a URL is provided to next-server that cannot be parsed, an unhandledPromiseRejection could occur. On Node.js versions < v15.0.0 this isn't a fatal issue as only a warning is shown. However, in Node.js versions > v15.0.0, this causes the server process to exit, which can result in unexpected server crashes.
npm install next@latest --savev11.1.0 and below v12.0.5v15.0.0 being usednext start or a custom serverWe recommend everyone to upgrade regardless of whether you can reproduce the issue or not.
If you are running Node.js > v15.0.0 with Next.js, you can filter any server error logs for ERR_INVALID_URL.
As Next.js has grown in popularity and usage by enterprises, it has received the attention of security researchers and auditors. We are thankful to GitHub user hopeless-programmer-online for their investigation and discovery of the original bug.
We've landed a patch that ensures this is handled properly so the unhandledPromiseRejection issue no longer occurs.
Regression tests for this attack were added to the security integration test suite
security@vercel.com. We are actively monitoring this mailbox.console.* calls.: #31449next lint without eslint-config-next installed: #29823.json static method: #31483Google-PageRenderer bot: #31521Document components an error: #31505Suspense import: #31897React import: #31900next export documentation.: #31465sharp memory usage on default Linux setup: with-sentry example: #30401Huge thanks to @mzaien, @losfair, @ykzts, @leerob, @timneutkens, @stefanprobst, @javivelasco, @sokra, @goncy, @knezevicdev, @Kikobeats, @huozhi, @shuding, @styfle, @yang-feng-yfeng, @kdy1, @xuchaobei, @elkevinwolf, @padmaia, @kyliau, @devknoll, @fabienheureux, @hanneslund, @nilskaspersson, @Andarist, @mathcrln, @ijjk, @dferber90, @molebox, @FranciscoMoretti, @benschwarz, @wendellhu95, @gazdagergo, @imabp, @ljosberinn, @samuliasmala, @lfades, @ka2jun8, @monsonjeremy, @pqt, @vvo, @leoortizz, @michel-kraemer, @thibautsabot, @MaedahBatool, @lobsterkatie, @ntkoopman, @delbaoliveira, @iicdii, @j-mendez, @chentsulin, @ericmatthys, @lennym, @balogunkeji, and @wnr for helping!
renderToWebStream: #31553no-html-link-for-pages from warning for static files: #31495next/link: #30606pages/_document: #31946