- Notifications
You must be signed in to change notification settings - Fork29.8k
[backport] fix: disable unknownatrules lint rule entirely (#83059)#83060
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
…e rule entirely (#83059)<!-- Thanks for opening a PR! Your contribution is much appreciated.To make sure your PR is handled as smoothly as possible we request thatyou follow the checklist sections below.Choose the right checklist for the change(s) that you're making:## For Contributors### Improving Documentation- Run `pnpm prettier-fix` to fix formatting issues before opening thePR.- Read the Docs Contribution Guide to ensure your contribution followsthe docs guidelines:https://nextjs.org/docs/community/contribution-guide### Adding or Updating Examples- The "examples guidelines" are followed from our contributing dochttps://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md- Make sure the linting passes by running `pnpm build && pnpm lint`. Seehttps://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md### Fixing a bug- Related issues linked using `fixes #number`- Tests added. See:https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs- Errors have a helpful link attached, seehttps://github.com/vercel/next.js/blob/canary/contributing.md### Adding a feature- Implements an existing feature request or RFC. Make sure the featurerequest has been accepted for implementation before opening a PR. (Adiscussion must be opened, seehttps://github.com/vercel/next.js/discussions/new?category=ideas)- Related issues/discussions are linked using `fixes #number`- e2e tests added(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)- Documentation added- Telemetry added. In case of a feature if it's used or not.- Errors have a helpful link attached, seehttps://github.com/vercel/next.js/blob/canary/contributing.md## For Maintainers- Minimal description (aim for explaining to someone not on the team tounderstand the PR)- When linking to a Slack thread, you might want to share details of theconclusion- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues- Add review comments if necessary to explain to the reviewer the logicbehind a change### What?### Why?### How?Closes NEXT-Fixes #-->
ztanner approved these changesAug 26, 2025
c8faf68 intonext-15-5 146 checks passed
Uh oh!
There was an error while loading.Please reload this page.
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Labels
create-next-appRelated to our CLI tool for quickly starting a new Next.js application. created-by: Next.js teamPRs by the Next.js team. locked
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Biome is close to releasing their fix for Tailwind parsing, but it'll be released in the next minor version.
We want to make sure that linting the template doesn't show any problems arising from Tailwind at-rules in the meantime.
(See#82974 and#82826)