ncc vs Rollup
ncc
github.com
Rollup
rollupjs.orgSide by side
| Figure | ncc | Rollup |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | — | Yes |
| Plans published | 1 | 0 |
| Spec score · JavaScript Build Tools | 8.2 (#5) | 7.3 (#20) |
| Configuration | The design goals include zero configuration and built-in TypeScript support. | Rollup configuration files are optional, and the documentation recommends them as a convenient way to configure advanced functionality. |
| Integrations | The package support guide gives configuration examples for Sequelize with MariaDB and for `@google-cloud/vision` with `google-proto-files`. | The site says Vite pre-configures Rollup with defaults and plugins, and names WMR as a project that adopted its plugin API. |
| License | The repository lists an MIT license. | Rollup is released under the MIT License. |
| Purpose | ncc is a CLI that compiles a Node.js module and its dependencies into a single file. | Rollup is a JavaScript module bundler that compiles smaller code modules into libraries or applications. |
| Use cases | The project lists publishing minimal npm packages and shipping only relevant app code to serverless environments as motivations. | The project describes Rollup as suitable for building libraries and applications, including builds targeting browsers and Node.js. |
Plans
In their own words
ncc
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.