c16e28715f
Supersedes #37750 as the overlay has been refactored and moved into the Next.js package itself. If it detects an older major version, it will show "outdated". Older minor shows "out of date". Old canary will show "out of date", with a different message. Matching latest canary or latest will show "up to date". It will show nothing if we could not detect the versions due to some error. <details> <summary>States: Fresh, stale, outdated</summary> Fresh: ![image](https://user-images.githubusercontent.com/18369201/208972067-8f2bd8d5-bb92-440a-a3aa-0685b18b4871.png) Stale: ![image](https://user-images.githubusercontent.com/18369201/208971789-baec0b90-718a-4cdc-bb15-ed23ce5efcbc.png) Outdated: ![image](https://user-images.githubusercontent.com/18369201/208972153-923ab865-e0f7-405d-9411-45ad1f545d0e.png) </details> Fixes NEXT-316 --------- Co-authored-by: Sukka <isukkaw@gmail.com> Co-authored-by: Steven <steven@ceriously.com> Co-authored-by: Hannes Bornö <hannes.borno@vercel.com> Co-authored-by: Hannes Bornö <borno.hannes@gmail.com> Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
1.4 KiB
1.4 KiB
Version Staleness
Why This Error Occurred
In the error overlay, a message was shown that the detected Next.js version was out-of-date.
To get the newest features and bug fixes, it is recommended to stay up to date.
Possible Ways to Fix It
If you are testing out a canary release, upgrade Next.js with one of the following:
npm i next@canary
yarn add next@canary
pnpm add next@canary
If you are using a stable release, upgrade Next.js with one of the following:
npm i next@latest
yarn add next@latest
pnpm add next@latest
If you are coming from an older major version, check out our upgrade guides.
Note
If you want to report a bug on GitHub, you should upgrade to the newest canary release of Next.js first, to see if the bug has already been fixed in canary.