mirror of
https://github.com/oxc-project/oxc.git
synced 2026-09-14 19:36:11 +08:00
0389c4010e
### 🚀 Features -83cb516minifier: Improve negation of expressions in boolean context (#25755) (Armano) ### 🐛 Bug Fixes -134fb22isolated-declarations: Preserve unresolved parameter types (#25909) (Dunqing) -526c2b3codegen: Remove deprecated test APIs (#25889) (camc314) -344a9b2codegen: Align enum template sourcemaps (#25872) (camc314) ### ⚡ Performance -5ef0c93minifier: Unwrap all unary exprs without creating dummy expressions (#25891) (Armano) -8783524packages/codegen: Remove loop from `growMappingBuffer` (#25886) (overlookmotel) -b6b14c0packages/codegen: Remove redundant branch (#25885) (overlookmotel) -be6adf0packages/sourcemap: Make `location` passed to `recordSourceMapping` always a number (#25884) (overlookmotel) -f720f15packages/codegen: Take named-mapping only code off hot path in `recordSourceMapping` (#25883) (overlookmotel) -a734af5packages/codegen: Remove redundant setting of `last` in `printImportAttributes` and `printIf` (#25882) (overlookmotel) -c6e44c6packages/codegen: Combine 2 writes in `printJSXElement` (#25881) (overlookmotel) -8801662packages/codegen: Remove redundant mapping from `printParams` (#25880) (overlookmotel) ### 📚 Documentation -5ad330epackages/codegen: Reformat comments (#25876) (overlookmotel)
⚓ Oxc
The Oxidation Compiler is a high-performance web toolchain. This is an umbrella crate re-exporting all of oxc's different tools. It also adds higher-level APIs for stitching various components together that are not found in other oxc crates.
⚡️ Quick Start
The easiest way to get started with oxc is by adding this to your Cargo.toml:
[dependencies]
oxc = { version = "*", features = ["full"] }
In most cases, code using oxc will follow this general pipeline:
- Parse source code into an AST
- Run semantic analysis on the AST
- Use the AST and semantic data in one or more other tools
- Generate new code for the final processed program
Example
This example performs the first two steps of this pipeline:
use std::path::Path;
use oxc::{
allocator::Allocator,
parser::{Parser, ParserReturn},
span::SourceType,
semantic::{SemanticBuilder, SemanticBuilderReturn}
};
// In real code, this will likely come from a file read from disk.
let source_path = Path::new("test.tsx");
let source_text = "
import React from 'react';
export interface Props {
count: number;
onInc: () => void;
onDec: () => void;
}
export const Counter: React.FC<Props> = props => {
return (
<div>
<button onClick={props.onInc}>+</button>
<span id='count'>{props.count}</span>
<button onClick={props.onDec}>-</button>
</div>
);
};
";
// Memory arena where AST nodes are allocated.
let allocator = Allocator::default();
// Infer source type (TS/JS/ESM/JSX/etc) based on file extension
let source_type = SourceType::from_path(source_path).unwrap();
let mut errors = Vec::new();
// Step 1: Parsing
// Parse the TSX file into an AST. The root AST node is a `Program` struct.
let ParserReturn { program, errors: parser_errors, panicked, .. } =
Parser::new(&allocator, source_text, source_type).parse();
errors.extend(parser_errors);
// Parsing failed completely. `program` is empty and `errors` isn't. If the
// parser could recover from errors, `program` will be a valid AST and
// `errors` will be populated. We can still perform semantic analysis in
// such cases (if we want).
if panicked {
for error in &errors {
eprintln!("{error:?}");
panic!("Parsing failed.");
}
}
// Step 2: Semantic analysis.
// Some of the more expensive syntax checks are deferred to this stage, and are
// enabled using `with_check_syntax_error`. You are not required to enable
// these, and they are disabled by default.
let SemanticBuilderReturn {
semantic,
errors: semantic_errors,
} = SemanticBuilder::new()
.with_check_syntax_error(true) // Enable extra syntax error checking
.with_cfg(true) // Build a Control Flow Graph
.build(&program); // Produce the `Semantic`
errors.extend(semantic_errors);
if errors.is_empty() {
println!("parsing and semantic analysis completed successfully.");
} else {
for error in errors {
eprintln!("{error:?}");
panic!("Failed to build Semantic for Counter component.");
}
}
// From here, you can now pass `program` and `semantic` to other tools.
💡 Features
These feature flags enable/disable various tools in oxc's toolchain:
full: Enable all features that provide access to a tool.semantic: Enable thesemanticmodule for semantic analysis on ASTs.transformer: Enable thetransformermodule for babel-like transpiling.minifier: Enable theminifierandmanglermodules for terser-like minification.codegen: Enable thecodegenmodule, which prints ASTs to source code and source maps.mangler: Enable themanglermodule without enablingminifier.cfg: Expose thecfgmodule. CFGs may still be created insemanticwithout turning this on.ast_visit: Enable theast_visitmodule for AST traversal.regular_expression: Enable regular expression parsing support.isolated_declarations: enable theisolated_declarationsmodule for generating typescript type declarations
These feature flags modify the behavior of oxc's tools. None of them are enabled
by the full feature.
serialize: ImplementsSerializeandDeserializefor various oxc data structures.conformance: Enables additional AST visitor hooks for conformance tests.
