oxc-project / oxc-project/backlog
tasks: automation around comparing to other tools
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
To reduce time on debugging our tools, we need a new tool for comparing against other tools.
How I imagine this should work:
pbpaste | cargo run -p compare -- bunch of args
cargo run -p compare -- bunch of args https://raw.github.com/...
cargo run -p compare -- bunch of args ./test.js
These commands will
- retrieve the file from clipboard / url / disk
- run all our components
- save each component's output to disk if we want to inspect the full output
- compare these outputs to babel / swc / esbuild etc
- run our output and other tool's output through prettier
- produce a diff if there are mismatches
I have been doing these tasks over and over, I think it's time to automate these steps.
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 with the proposed cargo run -p compare -- ... entry point and the ./test.js example; the issue does not name existing files or tests to inspect. Done would mean accepting clipboard, URL, and disk inputs, running the project components and comparison tools, optionally saving outputs, formatting with Prettier, and producing diffs for mismatches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, rust
- Domain
- cli, developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100