fix(eslint): respect pageExtensions in no-html-link-for-pages #88333
+43
−8
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
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
| * Recursively parse directory for page URLs. | ||
| */ | ||
| function parseUrlForPages(urlprefix: string, directory: string) { | ||
| const extensions = ['js', 'jsx', 'ts', 'tsx'] |
Contributor
There was a problem hiding this comment.
The no-html-link-for-pages ESLint rule doesn't respect custom pageExtensions from Next.js config, causing files with compound extensions like test.page.tsx to have incorrect URLs (e.g., /test.page/ instead of /test/)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #53473
This change updates the no-html-link-for-pages ESLint rule to correctly
handle custom pageExtensions such as *.page.tsx by avoiding hardcoded
file extension assumptions.
Added test coverage to ensure the rule warns correctly for pages using
custom extensions.
Note: Local Jest execution for this rule can be limited on Windows due
to the Next.js repo test setup; CI should validate the change.