Discover the Rust JS toolchain — oxlint, the Oxc parser, the resolver, and how it fits the Rust-tooling movement
0 / 5 completed
1 / 5
What is Oxc (the Oxidation Compiler)?
Oxc: is a suite of Rust-based JavaScript and TypeScript tooling components: an extremely fast parser, the oxlint linter, a module resolver, a transformer/minifier, and more. The project aims to provide foundational, reusable, high-speed building blocks for the JS toolchain ecosystem.
2 / 5
What is the main selling point of oxlint?
oxlint: targets speed, commonly reported as dozens of times faster than ESLint on large codebases because it is compiled Rust with multi-core parallelism and no per-file Node startup. It ships many rules out of the box and runs with zero configuration, making it ideal as a fast pre-commit or CI gate alongside or ahead of ESLint.
3 / 5
Why is the Oxc parser significant for other tools?
Oxc parser: produces an ESTree-compatible AST for JavaScript and TypeScript at very high speed. Because parsing is the foundation of linting, transforming, and bundling, a fast Rust parser becomes shared infrastructure — tools like Rolldown and oxlint build atop it rather than re-implementing parsing in JavaScript.
4 / 5
What role does the Oxc resolver play?
Oxc resolver: implements module resolution — Node's algorithm, package.jsonexports/imports conditions, and TypeScript paths mapping. As a standalone Rust crate it gives other tools a correct, fast way to turn an import like "@app/utils" into a concrete file, avoiding each tool writing its own resolver.
5 / 5
How does Oxc relate to the broader move toward Rust-based JS tooling?
Rust tooling trend: Oxc joins projects such as SWC, Biome, and Rolldown that rewrite the JS toolchain in Rust for order-of-magnitude performance improvements. The pattern is consistent: native-speed cores exposed through familiar JS/TS configuration, reducing CI time and local feedback loops for large codebases.