feat(linter): add hint about node version when ts config fail to import

[camc314]

fixes #20467

I tested this locally:

Failed to parse oxlint configuration file.

  x Failed to load config: <fixture>/oxlint.config.ts
  | 
  | TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for <fixture>/oxlint.config.ts
  | 
  | TypeScript config files require Node.js ^20.19.0 || >=22.12.0.
  | Detected Node.js v22.11.0.
  | Please upgrade Node.js or use a JSON config file instead.

[camc314]

• feat(linter): add hint about node version when ts config fail to import #20570 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent changes, fast-track this PR to the front of the merge queue

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Copilot]

Pull request overview

Adds a more actionable error hint when loading JS/TS config files fails due to Node.js lacking native TypeScript module support, so users get guided toward upgrading Node or using a JSON config instead.

Changes:

• Introduces a utility to detect “unknown file extension” failures for TS module specifiers and format a Node version upgrade hint.
• Wires that hint into loadJsConfigs() failure aggregation so it can be surfaced to users.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
apps/oxlint/src-js/utils/node_version.ts	New helper for detecting TS module load failures and generating a Node version hint.
apps/oxlint/src-js/js_config.ts	Uses the new helper to enrich config-import failure messages.

[overlookmotel]

The change looks correct, but a rather convoluted implementation! "is this a TS file" check could be as simple as:

const index = path.lastIndexOf(".");
const isTs = index >= 0 && ["ts", "mts", "cts"].includes(path.slice(index + 1));

And do we support .mts / .cts config files anyway?

But it's all on cold path, so I guess it doesn't really matter. The better error message is definitely desirable.

[overlookmotel]

Oh actually what I said in my last comment was wrong, due to ?cache=... being appended to path. But it sounds like Copilot's point is valid.

It might be simpler to just pass process.version from JS to Rust at process start-up, and handle this on Rust side. If TS is not supported, and they're using a TS config file, no point even calling into JS to try to load the config - we know it'll fail.

[camc314]

And do we support .mts / .cts config files anyway?

We support --config foo.mts for example.

It might be simpler to just pass process.version from JS to Rust at process start-up, and handle this on Rust side. If TS is not supported, and they're using a TS config file, no point even calling into JS to try to load the config - we know it'll fail.

this is a little more complex + we would have to handle bun/deno & other runtime versions i guess?

I think it's ok for this to be on the cold path on the JS side

[camc314]

Merge activity

• Mar 24, 11:47 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Mar 24, 11:47 AM UTC: camc314 added this pull request to the Graphite merge queue.
• Mar 24, 11:51 AM UTC: The Graphite merge queue couldn't merge this PR because it was not satisfying all requirements (Failed CI: 'Test NAPI Oxlint').
• Mar 25, 8:58 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Mar 25, 8:58 PM UTC: camc314 added this pull request to the Graphite merge queue.
• Mar 25, 8:58 PM UTC: Merged by the Graphite merge queue.