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.2 KiB
1.2 KiB
Opening a new Issue
Why This Message Occurred
When next info
was run, Next.js detected that it was not on the newest canary release.
next@canary
is the canary version of Next.js that ships daily. It includes all features and fixes that have not been released to the stable version yet. Think of canary as a public beta.
Some issues may already be fixed in the canary version, so please verify that your issue reproduces before opening a new issue.
Run the following in the codebase:
npm install next@canary
or
yarn add next@canary
And go through the prepared reproduction steps once again, and check if the issue still exists.