-
Notifications
You must be signed in to change notification settings - Fork 29.5k
fix(eslint): add support for custom pageExtensions in no-html-link-fo… #84626
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Srajal1311
wants to merge
1
commit into
vercel:canary
Choose a base branch
from
Srajal1311:fix/page-extensions-support
base: canary
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+27
−6
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new file extension check will never match because it tests the normalized URL (which has a trailing slash) against a regex that expects the string to end with a file extension.
View Details
📝 Patch Details
Analysis
File extension check never matches due to trailing slash from URL normalization
What fails: In
packages/eslint-plugin-next/src/rules/no-html-link-for-pages.ts
, theallowedExtRegex
check at line 172 never matches links with file extensions (.js
,.jsx
,.ts
,.tsx
) because it tests against the normalized URL which has a trailing slash appended.How to reproduce:
Result: Links to static files like
<a href="/public/script.js">
are incorrectly flagged by the ESLint rule, even though they should be skipped.Expected: The regex should match and skip these links, as they point to static resources rather than Next.js pages. Testing against the original
href.value.value
before normalization correctly identifies file extensions.Fix: Check for file extensions before URL normalization, since
normalizeURL()
appends a trailing slash that breaks the end-of-string anchor ($
) in the regex pattern.