b8c61a9c27
When triaging bug reports, we would like to make sure that our main focus is on unresolved issues. Next.js is a highly active project, and we cut new releases fairly often, under the `next@canary` tag. Some of the issues being reported might have already been fixed there, so we would like to encourage people to check them out. Once a fix is in `canary`, it will be included in the next `latest` release automatically. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples)
64 lines
3.7 KiB
YAML
64 lines
3.7 KiB
YAML
name: Bug Report
|
|
description: Create a bug report for the Next.js core
|
|
labels: 'template: bug'
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: Thanks for taking the time to file a bug report! Please fill out this form as completely as possible.
|
|
- type: markdown
|
|
attributes:
|
|
value: If you leave out sections there is a high likelihood it will be moved to the GitHub Discussions ["Help" section](https://github.com/vercel/next.js/discussions/categories/help).
|
|
- type: checkboxes
|
|
attributes:
|
|
label: Verify canary release
|
|
description: '`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.'
|
|
options:
|
|
- label: I verified that the issue exists in the latest Next.js canary release
|
|
required: true
|
|
- type: textarea
|
|
attributes:
|
|
label: Provide environment information
|
|
description: Please run `next info` in the root directory of your project and paste the results. You might need to use `npx --no-install next info` if next is not in the current PATH.
|
|
validations:
|
|
required: true
|
|
- type: input
|
|
attributes:
|
|
label: What browser are you using? (if relevant)
|
|
description: 'Please specify the exact version. For example: Chrome 100.0.4878.0'
|
|
- type: input
|
|
attributes:
|
|
label: How are you deploying your application? (if relevant)
|
|
description: 'For example: next start, next export, Vercel, Other platform'
|
|
- type: textarea
|
|
attributes:
|
|
label: Describe the Bug
|
|
description: A clear and concise description of what the bug is.
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
attributes:
|
|
label: Expected Behavior
|
|
description: A clear and concise description of what you expected to happen.
|
|
validations:
|
|
required: true
|
|
- type: input
|
|
attributes:
|
|
label: Link to reproduction
|
|
description: A link to a GitHub repository, a [StackBlitz](https://stackblitz.com/fork/github/vercel/next.js/tree/canary/examples/reproduction-template), or a [CodeSandbox](https://codesandbox.io/s/github/vercel/next.js/tree/canary/examples/reproduction-template) minimal reproduction. Minimal reproductions should be created from our [bug report template with `npx create next-app -e reproduction-template`](https://github.com/vercel/next.js/tree/canary/examples/reproduction-template) and should include only changes that contribute to the issue.
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
attributes:
|
|
label: To Reproduce
|
|
description: Steps to reproduce the behavior, please provide a clear description of how to reproduce the issue, based on the linked minimal reproduction. Screenshots can be provided in the issue body below. If using code blocks, make sure that [syntax highlighting is correct](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks#syntax-highlighting) and double check that the rendered preview is not broken.
|
|
validations:
|
|
required: true
|
|
- type: markdown
|
|
attributes:
|
|
value: Before posting the issue go through the steps you've written down to make sure the steps provided are detailed and clear.
|
|
- type: markdown
|
|
attributes:
|
|
value: Contributors should be able to follow the steps provided in order to reproduce the bug.
|
|
- type: markdown
|
|
attributes:
|
|
value: These steps are used to add integration tests to ensure the same issue does not happen again. Thanks in advance!
|