fix(eslint-plugin-next): respect pageExtensions in no-html-link-for-pages rule

[Jah-yee]

Fix

The @next/next/no-html-link-for-pages rule was ignoring the pageExtensions configuration from next.config.js, causing false negatives when users configured custom page extensions (e.g., page.tsx, page.ts).

Root Cause

In packages/eslint-plugin-next/src/utils/url.ts, the parseUrlForPages and parseUrlForAppDir functions used hardcoded regex /(\\.(j|t)sx?)$/ to detect page files, instead of using the configured pageExtensions.

Changes

1. url.ts:

   • parseUrlForPages now accepts a pageExtensions parameter and builds a dynamic regex from it
   • parseUrlForAppDir similarly respects pageExtensions for page.tsx and layout.tsx detection
   • getUrlFromPagesDirectories and getUrlFromAppDirectory now accept and pass pageExtensions
   • Default extensions remain ['jsx', 'js', 'ts', 'tsx'] for backward compatibility

2. no-html-link-for-pages.ts:

   • Reads pageExtensions from context.settings.next.pageExtensions
   • Passes it to getUrlFromPagesDirectories and getUrlFromAppDirectory

Usage

In your ESLint config:

{
  settings: {
    next: {
      pageExtensions: ['page.tsx', 'page.ts', 'jsx', 'js', 'ts', 'tsx']
    }
  }
}

Closes vercel#53473

[Jah-yee]

Closing this internal fork PR to tidy the queue; the upstream PR is the one to track. Happy to reopen here if a fork-only workflow is ever needed.

Upstream: vercel#92980