Closed styfle closed 2 weeks ago
Commit: 91434c6f2d217b931849d7d7739a6ae9e14a4a67
Commit: 0c0f8329096a6e9f54fe3a66d00d04224e93b461
pnpm test-start test/e2e/basepath.test.ts
Read more about building and testing Next.js in contributing.md.
TURBOPACK=1 pnpm test-start test/production/pages-dir/production/test/index.test.ts
(turbopack)
Read more about building and testing Next.js in contributing.md.
Looks like lint is failing because PR https://github.com/vercel/next.js/pull/61291 was force merged.
I'm going to force merge this one to unblock and lint can be fixed in a new PR.
I still get the error with next 14.1.4 and react ^18.2.0. Running next dev, not jest.
In a previous PR, https://github.com/vercel/next.js/pull/47302, detection for
fetchPriority
assumed that https://github.com/facebook/react/pull/25927 would land in react@18.3.0 because that was the react@canary version at the time. However, it didn't land in react@18.3.0 and it is expected to land in react@19.0.0 due to the breaking change.This means that users upgrading to react@18.3.0 will see a warning.
The fix is to stop looking at the
React.version
string and instead check forReact.use
, a feature that will land in react@19.0.0 but is also available in react@canary and react@beta today.Note: There were tests added for App Router and Pages Router in a previous PR https://github.com/vercel/next.js/pull/47302 but they seem to run on react@18.2.0 which is why we don't see failures.
Fixes https://github.com/vercel/next.js/issues/65161
Related https://github.com/facebook/react/issues/28946