ncc vs Parcel

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.

Parcel is a free, open source, zero-configuration build tool for web projects. It handles HTML, CSS, JavaScript, TypeScript, JSX, Flow, images, fonts, videos, Sass, SVG, Vue, Node, Electron, GraphQL, MDX, XML and other file types out of the box. It can automatically install plugins and development dependencies for additional file types. For development, Parcel includes an HTTPS server with an API proxy and automatically updates code in the browser, with React Fast Refresh and Vue hot-reloading integrations. Terminal and browser diagnostics include syntax-highlighted code frames, hints and documentation links. Production features include tree shaking, minification, image optimization, code splitting, content hashing, and Gzip and Brotli compression. Builds use worker threads and caching, with lazy development builds also supported. Parcel can target declared browser environments, handle workers, build libraries for multiple targets and build monorepos with one command. A plugin system and programmatic API support customization and integration into existing build systems. Its development server builds only one target at a time and defaults to a modern browser target; compression is not enabled by default.