ncc vs SWC

ncc is a free, MIT-licensed command-line tool for compiling a Node.js module and its dependencies into one file. It is distributed through npm as `@vercel/ncc`, with `npm i -g @vercel/ncc` given as the global installation command. The project targets publishing minimal npm packages and sending only relevant application code to serverless environments. Its design goals include zero configuration, built-in TypeScript support, and handling Node.js programs and npm modules. Inputs can include TypeScript, binary addons, and dynamic requires. Build options cover minification, source maps, watched builds, external modules, and ECMAScript target selection. Node.js programs can call ncc programmatically with options for caching, externals, minification, source maps, and asset builds. `.ts` and `.tsx` inputs require a `tsconfig.json`. Module-format behavior includes automatic ES module output for `.mjs` files and `.js` files inside a `type: module` package boundary. Support examples cover Sequelize with MariaDB and `@google-cloud/vision` with `google-proto-files`. Dynamically loaded assets that static analysis cannot identify may not work correctly. It runs on Linux.

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.