The React Framework
7 Nov 2024 · 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.
| Requirement | From15.0.2 on npm (opens in a new tab) | To15.0.3 on npm (opens in a new tab) |
|---|---|---|
Node.js | >=18.18.0 | ^18.18.0 || ^19.8.0 || >= 20.0.0 |
react | ^18.2.0 || 19.0.0-rc-02c0e824-20241028Required peer | ^18.2.0 || 19.0.0-rc-66855b96-20241106Required peer |
react-dom | ^18.2.0 || 19.0.0-rc-02c0e824-20241028Required peer | ^18.2.0 || 19.0.0-rc-66855b96-20241106Required peer |
basePath in findSourceMapURL: #71719pnpm-workspace.yaml to test fixtures to bypass PNPM workspace checks: #7172669d4b800-20241021 to 45804af1-20241021: #71718--turbopack flag when --turbo exists in next dev: #7173045804af1-20241021 to 28668d39-20241023: #7174528668d39-20241023 to 1631855f-20241023: #71769turbopack://[project]/... sourcemap uris with file://... in development: #71489--turbo to --turbopack if applicable: #71737"use cache": #71793--enable-source-maps by default in next dev: #71820registerClientReference for ESM client component modules: #71968await of params when metadata is used with an image file: #718711631855f-20241023 to 02c0e824-20241028: #71979ignoreList when Webpack is used: #71821next-dynamic-access-named-export: #72016__turbopack_original__ while tree shaking: #71547"use cache" on before code snippet: #71815packages/next/src/compiled: #71986use cache: Add text code formatting: #71999cacheTag Function Usage: #71912use cache comments : #71981Huge thanks to @ytori, @unstubbable, @huozhi, @SebassNoob, @tatsuteb, @Marukome0743, @gnoff, @samcx, @devjiwonchoi, @imprakharshukla, @migueldamota, @eps1lon, @ztanner, @timneutkens, @cantemizyurek, @sebmarkbage, @padmaia, @ijjk, @styfle, @wbinnssmith, @feedthejim, @kdy1, @shuding, @molebox, @ismaelrumzan, @sokra, @bgw, @timeyoutakeit, @AdonisAgelis, @chicoxyzzy, @gaojude, @elitalpa, @t3dotgg, @gaearon, @nisabmohd, @gadcam, @delbaoliveira, @bennettdams, @wiscaksono, and @Developerayo for helping!