Skip to content

docs(eslint): clarify note for no-html-link-for-pages rule #83493

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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: canary
Choose a base branch
from
Open

docs(eslint): clarify note for no-html-link-for-pages rule #83493

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/01-app/03-api-reference/05-config/03-eslint.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,9 @@ The full set of rules is as follows:
| <Check size={18} /> | @next/next/no-typos | Prevent common typos in [Next.js's data fetching functions](/docs/pages/building-your-application/data-fetching) |
| <Check size={18} /> | [@next/next/no-unwanted-polyfillio](/docs/messages/no-unwanted-polyfillio) | Prevent duplicate polyfills from Polyfill.io. |

> **Note:** The rule `@next/next/no-html-link-for-pages` does **not currently detect pages** when using custom `pageExtensions` (e.g., `.mdx` or `.page.tsx`).
> You may need to disable this rule or configure ESLint manually until support is added. See [issue #53473](https://github.com/vercel/next.js/issues/53473).

We recommend using an appropriate [integration](https://eslint.org/docs/user-guide/integrations#editors) to view warnings and errors directly in your code editor during development.

## Examples
Expand Down
Loading