nodejs / nodejs/orchestrion-js
Evaluate if we should use oxc instead of swc
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 24
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
might give us some more performance wins, I think the DX for the rust types is also a little better.
There is also https://www.npmjs.com/package/oxc-parser
Contributor guide
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 https://oxc.rs/ and the oxc-parser npm package, then compare them with the repository's current swc usage. Define the performance and Rust developer-experience criteria for the evaluation, and document a clear recommendation about whether adopting oxc is justified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100