feat(eslint-plugin-next): add pageExtensions
option
#54474
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.
For Contributors
Improving Documentation
pnpm prettier-fix
to fix formatting issues before opening the PR.Adding or Updating Examples
pnpm build && pnpm lint
. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.mdAdding a feature
fixes #number
For Maintainers
What?
This PR is to fix a problem where @next/next/no-html-link-for-pages doesn't work when pageExtensions are configured.
As to why a new option should be provided, see the commend.
How?
An ESLint option called pageExtensions is provided.
Options Type
The rule accepts the following options:
The values can be:
string
- It's equivalent to thepagesDir
argument.string[]
- It's equivalent to thepagesDir
argument.pagesDir
- a path to a directory or an array of paths to directoriespageExtensions
- a string or an array of strings representing the extensions of the page filesUsage
If you set the
pageExtensions
config, this rule will not work and thepageExtensions
option must be set for it to work.Fixes #53473