Docs: add oxc-node to https://oxc.rs documentation
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- rust
- Domain
- documentation
Research direction
Start by reviewing the existing documentation at oxc.rs and the oxc-node project references to see how features are currently presented. Add oxc-node as a listed feature with documentation covering its intended TypeScript execution use cases and comparison with tsx; done means users can find and understand the feature from the site.
Written by the indexing model from the issue text.
Description
Hello!
Is it possible to add oxc-node as a listed feature in the oxc.rs/ docs? I couldn't find any references there. I think it's a missed opportunity to publicize a very useful feature.
My team currently uses tsx.is for "invoking typescript" in development tasks (running server in dev mode, and running some development or CI/CD scripts). If oxc-node could have docs and rough feature-parity with tsx, we could switch over and eliminate having a separate build stack for these use-cases.
Thanks again for the great project.
- Dominant language
- TypeScript
- Stars
- 244
- Forks
- 7
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 47
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from oxc-project/oxc-node
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oxc-project/oxc-node#804 ·
Maintainers usually reply within 1 day
-
`.cts` files with `import`/`export` fail differently depending on how they are loadedPossibly taken @Brooooooklyn claimed this today. Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
oxc-project/oxc-node#811 ·
Maintainers usually reply within 1 day
-
Standard (TC39) decorators fail with a bare `SyntaxError` at `@` instead of an actionable errorOpen
Difficulty 3/5 1-2 days Newbie friendliness 68/100
oxc-project/oxc-node#809 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
oxc-project/oxc-node#808 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
oxc-project/oxc-node#807 ·
Maintainers usually reply within 1 day
All issues in oxc-project/oxc-node
Similar issues
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 75/100
lingdojo/kana-dojo#32018 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
paperclipai/paperclip#15751 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
BuilderIO/agent-native#7275 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day