ncc vs Vite

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.

Vite is a free build tool for modern web projects. Its development server serves source files on demand using native ES modules and supports Hot Module Replacement. For production, the `vite build` command bundles application assets for static hosting. Vite supports TypeScript, JSX, CSS, web workers, and WebAssembly; plugins can extend the tool, including its development server and SSR functionality. Its plugin interface builds on Rollup's. Documented framework integrations include Vue, React, Preact, Svelte, Solid, Qwik, Nuxt, SvelteKit, Astro, and React Router. Developers can try Vite in a browser through StackBlitz using supported framework templates. It runs on Linux, macOS, Windows, and the web, and is MIT licensed and free and open source. Vite requires Node.js 20.19+ or 22.12+, though some templates may need a higher version. It transpiles TypeScript but does not type-check it; type checking needs to be handled separately. Legacy browser support can be added with the official `@vitejs/plugin-legacy`.