⚓ Oxc

The Oxidation Compiler is creating a suite of high-performance tools for JavaScript and TypeScript.

Oxc is building a parser, linter, formatter, transpiler, minifier, resolver ... all written in Rust.

💡 Philosophy

This project shares the same philosophies as Biome and Ruff.

1. JavaScript tooling could be rewritten in a more performant language.
2. An integrated toolchain can tap into efficiencies that are not available to a disparate set of tools.

⚡️ Quick Start

The linter is ready to catch mistakes for you. It comes with over 60 default rules and no configuration is required.

To start using, install oxlint or via npx:

npx oxlint@latest

To give you an idea of its capabilities, here is an example from the vscode repository, which finishes linting 4000+ files in 0.5 seconds.

⚡️ Performance

• The parser aim to be the fastest Rust-based ready-for-production parser.
• The linter is more than 50 times faster than ESLint, and scales with the number of CPU cores.

⌨️ Programming Usage

Rust

Individual crates are published, you may use them to build your own JavaScript tools.

• The umbrella crate oxc exports all public crates from this repository.
• The AST and parser crates oxc_ast and oxc_parser are production ready.
• See crates/*/examples for example usage.

While Rust has gained a reputation for its comparatively slower compilation speed, we have dedicated significant effort to fine-tune the Rust compilation speed. Our aim is to minimize any impact on your development workflow, ensuring that developing your own Oxc based tools remains a smooth and efficient experience.

This is demonstrated by our CI runs, where warm runs complete in 5 minutes.

Node.js

• You may use the parser via napi: oxc-parser

---

🎯 Tools

• AST and Parser
• Linter
• Resolver
• Minifier
• Formatter
• Transpiler
• Ezno Type Checker

🔸 AST and Parser

Oxc maintains its own AST and parser, which is by far the fastest and most conformant JavaScript and TypeScript (including JSX and TSX) parser written in Rust.

As the parser often represents a key performance bottleneck in JavaScript tooling, any minor improvements can have a cascading effect on our downstream tools. By developing our parser, we have the opportunity to explore and implement well-researched performance techniques.

While many existing JavaScript tools rely on estree as their AST specification, a notable drawback is its abundance of ambiguous nodes. This ambiguity often leads to confusion during development with estree.

The Oxc AST differs slightly from the estree AST by removing ambiguous nodes and introducing distinct types. For example, instead of using a generic estree Identifier, the Oxc AST provides specific types such as BindingIdentifier, IdentifierReference, and IdentifierName. This clear distinction greatly enhances the development experience by aligning more closely with the ECMAScript specification.

🏆 Parser Performance

Our benchmark reveals that the Oxc parser surpasses the speed of the swc parser by approximately 2 times and the Biome parser by 3 times.

How is it so fast?

• AST is allocated in a memory arena (bumpalo) for fast AST memory allocation and deallocation.
• Short strings are inlined by CompactString.
• No other heap allocations are done except the above two.
• Scope binding, symbol resolution and some syntax errors are not done in the parser, they are delegated to the semantic analyzer.

🔸 Linter

The linter embraces convention over configuration, eliminating the need for extensive configuration and plugin setup. Unlike other linters like ESLint, which often require intricate configurations and plugin installations (e.g. @typescript-eslint), our linter only requires a single command that you can immediately run on your codebase:

npx oxlint@latest

We also plan to port essential plugins such as eslint-plugin-import and eslint-plugin-jest.

🏆 Linter Performance

The linter is 50 - 100 times faster than ESLint depending on the number of rules and number of CPU cores used. It completes in less than a second for most codebases with a few hundred files and completes in a few seconds for larger monorepos. See bench-javascript-linter for details.

As an upside, the binary is approximately 3MB, whereas ESLint and its associated plugin dependencies can easily exceed 100.

You may also download the linter binary from the latest release tag as a standalone binary, this lets you run the linter without a Node.js installation in your CI.

How is it so fast?

• Oxc parser is used.
• AST visit is a fast operation due to linear memory scan from the memory arena.
• Files are linted in a multi-threaded environment, so scales with the total number of CPU cores.
• Every single lint rule is tuned for performance.

Linter Plugin

We are currently developing a DSL-based plugin system. The plugin system uses trustfall as its query engine and a subset of GraphQL as its query language.

You will not need to use JavaScript or Rust to write a plugin, this is useful for QAs and security researchers.

🔸 Resolver

Module resolution plays a crucial role in JavaScript tooling, especially for tasks like multi-file analysis or bundling. However, it can often become a performance bottleneck. To address this, we are actively working on porting enhanced-resolve.

eslint-plugin-import will be our first application for the resolver, since it is currently a performance and complexity blocker for a lot of projects.

🔸 Transpiler

A transpiler is responsible for turning higher versions of ECMAScript to a lower version that can be used in older browsers. We are currently focusing on an esnext to es2015 transpiler. See the umbrella issue for details.

🔸 Minifier

JavaScript minification plays a crucial role in optimizing website performance as it reduces the amount of data sent to users, resulting in faster page loads. This holds tremendous economic value, particularly for e-commerce websites, where every second can equate to millions of dollars.

However, existing minifiers typically require a trade-off between compression quality and speed. You have to choose between the slowest for the best compression or the fastest for less compression. But what if we could develop a faster minifier without compromising on compression?

We are actively working on a prototype that aims to achieve this goal, by porting all test cases from well-known minifiers such as google-closure-compiler, terser, esbuild, and tdewolff-minify.

Preliminary results indicate that we are on track to achieve our objectives. With the Oxc minifier, you can expect faster minification times without sacrificing compression quality.

🔸 Formatter

While prettier has established itself as the de facto code formatter for JavaScript, there is a significant demand in the developer community for a less opinionated alternative. Recognizing this need, our ambition is to undertake research and development to create a new JavaScript formatter that offers increased flexibility and customization options. Unfortunately we are currently lacking the resources to do so.

🔸 Ezno Type Checker

Developed by @kaleidawave, ezno is a TypeScript checker written in Rust with a focus on static analysis and runtime performance. You may read the announcement blog post for more information.

The type checker is available via npx oxidation-compiler@latest check path and the playground.

---

✍️ Contribute

See CONTRIBUTING.md for guidance.

Check out some of the good first issues or ask us on Discord.

If you are unable to contribute by code, you can still participate by:

• Add a GitHub Star to the project.
• Join us on Discord.
• Follow me on twitter and tweet about this project.

📚 Learning Resources

• My small tutorial on how to write a JavaScript Parser in Rust
• My small article Pursuit of Performance on Building a JavaScript Compiler
• Crafting Interpreters
• Andrew Kelley - Practical DOD

🧑‍💻 Maintenance

Oxc is being maintained by Boshen as the project lead with the help of contributors from all over the world.

Rules of thumb:

• APIs should be simple and well-documented.
• All performance issues (runtime and compilation speed) are considered as bugs in this project.
• Third-party dependencies should be minimal.
• Monitor code coverage for unused code. Aim for 99% code coverage.
• Embrace data-oriented design.
• Prefer smaller PRs. Try graphite.dev.

🤝 Credits

This project was incubated with the assistance of these exceptional mentors and their projects:

• Biome - @ematipico
• Ruff - @charliermarsh, @MichaReiser
• quick-lint-js - @strager
• elm-review - @jfmengels

Special thanks go to

• @domonji for contribution to the TypeScript parser
• @guan-wy for the project logo

And also

• @kaleidawave for Ezno Type Checker
• @zackradisic for tyvm
• @u9g for the work in progress oxc_linter_plugin

📖 License

Oxc is free and open-source software licensed under the MIT License.

Oxc partially copies code from the following projects, their licenses are listed in Third-party library licenses.

Project	License
eslint/eslint	MIT
typescript-eslint/typescript-eslint	MIT
import-js/eslint-plugin-import	MIT
jest-community/eslint-plugin-jest	MIT
microsoft/TypeScript	Apache 2.0
biomejs/biome	MIT
mozilla-spidermonkey/jsparagus	MIT Apache 2.0
prettier/prettier	MIT
acorn	MIT
zkat/miette	Apache 2.0
sindresorhus/globals	MIT
terser	BSD
evanw/esbuild	MIT
google/closure-compiler	Apache 2.0
tdewolff/minify	MIT
parcel-bundler/parcel	MIT
dividab/tsconfig-paths	MIT
tmccombs/json-comments-rs	Apache 2.0