44d1a1cb15
This PR is part of a larger effort to migrate error messages to MDX and use App Router: https://github.com/vercel/front/pull/23459
33 lines
1.2 KiB
Text
33 lines
1.2 KiB
Text
---
|
|
title: 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:
|
|
|
|
```bash filename="Terminal"
|
|
npm install next@canary
|
|
```
|
|
|
|
or
|
|
|
|
```bash filename="Terminal"
|
|
yarn add next@canary
|
|
```
|
|
|
|
And go through the prepared reproduction steps once again, and check if the issue still exists.
|
|
|
|
## Useful Links
|
|
|
|
- [Video: How to Contribute to Open Source (Next.js)](https://www.youtube.com/watch?v=cuoNzXFLitc)
|
|
- [Contributing to Next.js](https://github.com/vercel/next.js/blob/canary/contributing.md)
|
|
- [Triaging issues](https://github.com/vercel/next.js/blob/canary/contributing/repository/triaging.md)
|
|
- [Verifiying canary](https://github.com/vercel/next.js/blob/canary/.github/actions/issue-validator/canary.md)
|
|
- [Adding a reproduction](https://github.com/vercel/next.js/blob/canary/.github/actions/issue-validator/repro.md)
|