next.js: `@next/next/no-html-link-for-pages` rule does not work with `pageExtensions`
Verify canary release
- I verified that the issue exists in the latest Next.js canary release
Provide environment information
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 22.5.0: Thu Jun 8 22:22:20 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6000
Binaries:
Node: 18.14.2
npm: 9.8.1
Yarn: 1.22.19
pnpm: 8.3.1
Relevant Packages:
next: 13.4.13-canary.9
eslint-config-next: 13.4.12
react: 18.2.0
react-dom: 18.2.0
typescript: 5.1.3
Next.js Config:
output: N/A
Which area(s) of Next.js are affected? (leave empty if unsure)
ESLint (eslint-config-next)
Link to the code that reproduces this issue or a replay of the bug
https://github.com/nnmax/next-eslint-config-reproduction-app
To Reproduce
git clone https://github.com/nnmax/next-eslint-config-reproduction-app.gitcd next-eslint-config-reproduction-appnpm installnpm run lint- Observe the ESLint output from the terminal.
Describe the Bug
The @next/next/no-html-link-for-pages rule doesn’t work after configuring custom pageExtensions.
Expected Behavior
It should recognize pageExtensions.
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
About this issue
- Original URL
- State: open
- Created 3 years ago
- Comments: 15 (2 by maintainers)
Commits related to this issue
- Docs: Standardize terminology to 'filesystem' #53473 — committed to nguye3hg/next.js by nguye3hg 2 years ago
@abhishek1810
It looks like this is already being worked on for a duplicate ticket. Here’s the PR: https://github.com/vercel/next.js/pull/51783
Maybe reviewing and commenting on that PR first would be helpful.
Currently, the ESLint rule is indeed unaware of this configuration.
See https://github.com/vercel/next.js/blob/e757cac3f4c9152209537f8274e29e41a470920b/packages/eslint-plugin-next/src/rules/no-html-link-for-pages.ts#L95