feat(linter): implement oxlint.config.ts support

[camc314]

Refs: #17527

note: this does not include language server support

[camc314]

• feat(vscode): watch `oxlint.config.ts #18599
• feat(linter/lsp): add support for dynamic configs #18598
• feat(linter): auto generate oxlint.config.ts types #18597
• feat(oxlint): introduce defineConfig helper #18596
• feat(linter): implement oxlint.config.ts support #17563 👈 (View in Graphite)
• refactor(linter): rename DEFAULT_OXLINTRC to `DEFAULT_OXLINTRC_NAME #18666
• 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 hot fixes, skip the queue and merge this PR next

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.

[camc314]

Merge activity

• Feb 1, 10:45 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Feb 1, 11:10 PM UTC: camc314 added this pull request to the Graphite merge queue.
• Feb 1, 11:17 PM UTC: Merged by the Graphite merge queue.

[Copilot]

Pull request overview

This pull request implements support for TypeScript configuration files (oxlint.config.ts) in oxlint, enabling users to define linting configurations using TypeScript/JavaScript instead of JSON. This addresses issue #17527 and provides a more flexible configuration system for complex rule configurations, particularly in large monorepos where different teams maintain separate linting configs.

Changes:

• Added TypeScript config file support (oxlint.config.ts) with conflict detection to prevent both JSON and TS configs in the same directory
• Implemented parallel JS/TS config loading through Node.js with proper error handling for missing runtime, invalid exports, and execution errors
• Extended config discovery to detect both .oxlintrc.json and oxlint.config.ts files, with validation and override support

Reviewed changes

Copilot reviewed 29 out of 30 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
apps/oxlint/src/run.rs	Wires up JS config loader callback to CLI runner through NAPI interface
apps/oxlint/src/lint.rs	Adds config loader callback support to CliRunner with conditional compilation
apps/oxlint/src/lib.rs	Exports new js_config module and defines TS config filename constant
apps/oxlint/src/js_config.rs	Implements Rust-side JS config loader with JSON response parsing and error handling
apps/oxlint/src/config_loader.rs	Extends config discovery and loading to support TS files with conflict detection
apps/oxlint/src/lsp/server_linter.rs	Updates error handling to support configs without paths
apps/oxlint/src-js/js_config.ts	Implements Node.js-side config loading using dynamic imports with validation
apps/oxlint/test/fixtures/js_config_*	Comprehensive test fixtures covering basic usage, errors, conflicts, and overrides

Comments suppressed due to low confidence (1)

apps/oxlint/src/run.rs:14

• The same cfg attribute is applied twice in succession (lines 13 and 14). This is likely a mistake. One should be #[cfg(not(all(target_pointer_width = "64", target_endian = "little")))] and the other should be #[cfg(all(target_pointer_width = "64", target_endian = "little"))]. Currently, line 13 has the negation but line 14 doesn't negate it, so the import is only effective on 64-bit little-endian platforms. However, having both attributes on the same item means the second one overrides the first, making line 13 ineffective.

use crate::{
    init::{init_miette, init_tracing},

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.