No description
Find a file
2023-02-27 03:10:02 +08:00
.cargo feat(tasks): add parser benchmark 2023-02-11 08:46:32 -08:00
.github/workflows ci: attempt to fix miri with "-Zmiri-disable-isolation" 2023-02-26 00:49:19 +08:00
benchmark Git ignore benchmark/package-lock.json 2023-02-26 20:17:05 +08:00
crates fix(oxc_parser): check access correctly 2023-02-27 03:10:02 +08:00
tasks fix(oxc_parser): check access correctly 2023-02-27 03:10:02 +08:00
.gitignore chore: igore .js(x), .ts(x) in root directory 2023-02-26 02:02:05 +08:00
.gitmodules chore(tasks): update submodules 2023-02-24 13:08:22 +08:00
Cargo.lock feat(cli): support linting glob patterns 2023-02-26 22:25:16 +08:00
Cargo.toml feat(cli): support linting glob patterns 2023-02-26 22:25:16 +08:00
CONTRIBUTING.md chore: update contribution docs 2023-02-24 13:24:42 +08:00
LICENSE Initial commit 2023-02-09 13:46:52 +08:00
README.md Update README.md 2023-02-25 21:49:04 +08:00
rust-toolchain.toml chore: add rust-toolchain.toml and Cargo.toml 2023-02-11 13:03:40 +08:00
rustfmt.toml chore: add rustfmt.toml 2023-02-11 13:11:17 +08:00

The JavaScript Oxidation Compiler (oxc)

Why this project?

The goal of this project is to:

  • Create a blazingly fast JavaScript Compiler written in Rust.
  • Provide good documentation on learning Rust and compiler techniques.
  • Create a linter.

And mostly importantly, an invitation for you to come and learn Rust with me. We will learn a lot from each other!

You can watch this project and also follow me on twitter if you don't have the time to Rust but would like to learn things.

Contributing

Contributions are welcome and highly appreciated. To get started, check out CONTRIBUTING.md.

Call for action

You can take a look at some of the good first issues if you want to practice some Rust.

I welcome all nitpickings and bikesheddings if you think any of the code can be improved, just make an issue.

I have also created some discussions for documenting my thought processes.

Milestone

Oxc has a fully working parser and a prototype for the linter right now.

The current objectives are:

  • A MVP (Most Viable Product) for the linter.
  • Improve the parser for real usage. Areas include:

Parser Conformance

The cargo coverage command currently reports the following summary

Test262 Summary:
AST Parsed     : 43934/43934 (100.00%)

Babel Summary:
AST Parsed     : 2045/2057 (99.42%)

TypeScript Summary:
AST Parsed     : 4291/4861 (88.27%)

(The parser is failing some of the TypeScript recoverable parser tests.)

Linter Performance

See benchmark for details. Hyperfine results are:

Benchmark 1: oxc
  Time (mean ± σ):      30.9 ms ±   1.4 ms    [User: 138.2 ms, System: 54.7 ms]
  Range (min … max):    28.6 ms …  35.7 ms    83 runs

Benchmark 2: rome
  Time (mean ± σ):     145.0 ms ±   2.8 ms    [User: 674.9 ms, System: 69.9 ms]
  Range (min … max):   141.5 ms … 151.8 ms    19 runs

  Warning: Ignoring non-zero exit code.

Benchmark 3: eslint
  Time (mean ± σ):      2.661 s ±  0.057 s    [User: 4.076 s, System: 0.223 s]
  Range (min … max):    2.593 s …  2.790 s    10 runs

  Warning: Ignoring non-zero exit code.

Summary
  'oxc' ran
    4.70 ± 0.23 times faster than 'rome'
   86.20 ± 4.35 times faster than 'eslint'

Learning Resources

Credits

This project is inspired by the following great mentors and projects:

License

MIT