oxc-project / oxc-project/oxc-node
js `import` function for dynamic ts support
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 235
- Forks
- 7
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 38
Description
oxlint-migrate has some request to support eslint.config.ts out of the box without any configuration.
See https://github.com/oxc-project/oxlint-migrate/issues/109
Normally, the user needs one of this configuration:
npx --node-options="--import @oxc-node/core/register" @oxlint/migrate
npx --node-options="--import jiti/register" @oxlint/migrate
And experimental for node:
npx --node-options="--experimental-strip-types" @oxlint/migrate
ESLint itself supports jiti.import out of the box without extra arguments:
https://github.com/eslint/eslint/blob/4ab44823df4d4b47d3650da949077a0551e7579e/lib/config/config-loader.js#L141-L175
Questions
Is it possible to have the same functionality with oxc-node?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked ESLint config-loader.js implementation and the existing oxc-node import entry points. Trace how oxlint-migrate currently loads eslint.config.ts under the documented Node options, then define tests showing that the same file loads without extra configuration. Done means dynamic TypeScript config loading works through the supported oxc-node API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, rust, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100