ncc

Simple CLI for compiling a Node.js module into a single file, together with all its dependencies, gcc-style.

Motivation

• Publish minimal packages to npm
• Only ship relevant app code to serverless environments
• Don't waste time configuring bundlers
• Generally faster bootup time and less I/O overhead
• Compiled language-like experience (e.g.: go)

Design goals

• Zero configuration
• TypeScript built-in
• Only supports Node.js programs as input / output
• Support all Node.js patterns and npm modules

Usage

Installation

1npm i -g @vercel/ncc

Usage

1$ ncc <cmd> <opts>

Eg:

1$ ncc build input.js -o dist

If building an .mjs or .js module inside a "type": "module" package boundary, an ES module output will be created automatically.

Outputs the Node.js compact build of input.js into dist/index.js.

Note: If the input file is using a .cjs extension, then so will the corresponding output file. This is useful for packages that want to use .js files as modules in native Node.js using a "type": "module" in the package.json file.

Commands:

  build <input-file> [opts]
  run <input-file> [opts]
  cache clean|dir|size
  help
  version

Options:

  -o, --out [dir]          Output directory for build (defaults to dist)
  -m, --minify             Minify output
  -C, --no-cache           Skip build cache population
  -s, --source-map         Generate source map
  -a, --asset-builds       Build nested JS assets recursively, useful for
                           when code is loaded as an asset eg for workers.
  --no-source-map-register Skip source-map-register source map support
  -e, --external [mod]     Skip bundling 'mod'. Can be used many times
  -q, --quiet              Disable build summaries / non-error outputs
  -w, --watch              Start a watched build
  -t, --transpile-only     Use transpileOnly option with the ts-loader
  --v8-cache               Emit a build using the v8 compile cache
  --license [file]         Adds a file containing licensing information to the output
  --stats-out [file]       Emit webpack stats as json to the specified output file
  --target [es]            ECMAScript target to use for output (default: es2015)
                           Learn more: https://webpack.js.org/configuration/target
  -d, --debug              Show debug logs

Execution Testing

For testing and debugging, a file can be built into a temporary directory and executed with full source maps support with the command:

1$ ncc run input.js

With TypeScript

The only requirement is to point ncc to .ts or .tsx files. A tsconfig.json file is necessary. Most likely you want to indicate es2015 support:

1{
2  "compilerOptions": {
3    "target": "es2015",
4    "moduleResolution": "node"
5  }
6}

If typescript is found in devDependencies, that version will be used.

Package Support

Some packages may need some extra options for ncc support in order to better work with the static analysis.

See package-support.md for some common packages and their usage with ncc.

Programmatically From Node.js

1require('@vercel/ncc')('/path/to/input', {
2  // provide a custom cache path or disable caching
3  cache: "./custom/cache/path" | false,
4  // externals to leave as requires of the build
5  externals: ["externalpackage"],
6  // directory outside of which never to emit assets
7  filterAssetBase: process.cwd(), // default
8  minify: false, // default
9  sourceMap: false, // default
10  assetBuilds: false, // default
11  sourceMapBasePrefix: '../', // default treats sources as output-relative
12  // when outputting a sourcemap, automatically include
13  // source-map-support in the output file (increases output by 32kB).
14  sourceMapRegister: true, // default
15  watch: false, // default
16  license: '', // default does not generate a license file
17  target: 'es2015', // default
18  v8cache: false, // default
19  quiet: false, // default
20  debugLog: false // default
21}).then(({ code, map, assets }) => {
22  console.log(code);
23  // Assets is an object of asset file names to { source, permissions, symlinks }
24  // expected relative to the output code (if any)
25})

When watch: true is set, the build object is not a promise, but has the following signature:

1{
2  // handler re-run on each build completion
3  // watch errors are reported on "err"
4  handler (({ err, code, map, assets }) => { ... })
5  // handler re-run on each rebuild start
6  rebuild (() => {})
7  // close the watcher
8  void close ();
9}

Caveats

• Files / assets are relocated based on a static evaluator. Dynamic non-statically analyzable asset loads may not work out correctly