Oxc vs SWC

Oxc is a free collection of JavaScript tools written in Rust, available for Linux, macOS and Windows. Its toolchain includes a linter, formatter, parser, transformer, resolver, minifier and TypeScript runner. Oxlint checks JavaScript and TypeScript, including JSX, TSX and script blocks in Vue, Svelte and Astro files. It includes more than 870 rules across areas such as TypeScript, React, Jest, Vitest, imports, Unicorn and accessibility. Type-aware linting uses tsgo, a native Go port of the TypeScript compiler. Oxfmt follows a Prettier-compatible workflow and can sort imports, Tailwind CSS classes and package.json fields; it formats JavaScript, TypeScript, JSON, YAML, TOML, HTML, Vue, Svelte, CSS, Markdown, GraphQL and other formats. The transformer handles TypeScript and JSX, syntax lowering from ES2026 to ES2015, React Refresh, plugins and isolated declaration output. An experimental runner executes TypeScript and JSX without a separate build step, with ESM, CommonJS, source map and tsconfig.json support. It strips types but does not type-check programs, and its APIs and behavior may change between releases.

SWC is a free, extensible Rust-based platform for tools that compile and bundle JavaScript and TypeScript. It transforms modern JavaScript and TypeScript into code intended for major browsers, and supports minification, WebAssembly transforms, and custom plugins. Its core API parses ECMAScript, TypeScript, and Flow syntax; the documentation describes that API as mainly useful to build-tool authors. Integrations include webpack, Rspack, and Jest, while Next.js, Parcel, and Deno are among the tools named as users. A WebAssembly module can transform code synchronously inside a browser. SWC can be installed as prebuilt binaries or built from source, with packages documented for npm, Yarn, pnpm, Bun, and Deno. The site states that it is 20x faster than Babel on one thread and 70x faster on four cores. The bundling documentation says that feature will be dropped in v2 and recommends SWC-based bundlers instead. It also warns that its polyfill usage mode is less efficient than Babel for certain dynamically computed property expressions.