# 使用 Homebrew 安装 ncc

查看 ncc 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。

## 安装

```sh
sudo av install brew:ncc
```

其他安装命令:

### macOS

- Homebrew (100%):

```sh
brew install ncc
```

  证据: local Homebrew formula metadata

## 软件包事实

- **软件包键:** brew:ncc
- **软件包管理器:** Homebrew
- **版本:** 0.44.1
- **来源摘要:** Compile a Node.js project into a single file
- **主页:** <https://github.com/vercel/ncc>
- **最后更新:** 2026-07-01T00:51:23Z
- **已生成:** 2026-08-03T19:37:03+00:00

## 可执行文件

- ncc (别名)

## 安装行为

- Bottle: 不可用

## 版本和新鲜度

- 页面生成时间: 2026-08-03
- 管理器版本: 0.44.1
## 项目历史与用法

ncc is Vercel's zero-config Node.js bundler CLI for compiling a Node module and its dependencies into a single output file, with TypeScript support, asset handling, source maps, minification, externals, cache commands, and programmatic API support.

### 项目历史

The repository was created on 2018-11-13, with early package distribution under @zeit/ncc on npm the same day. After Zeit became Vercel, @vercel/ncc was created on npm on 2020-08-12 while the old @zeit/ncc package remained visible for legacy users.

The README describes the motivation plainly: publish minimal npm packages, ship only relevant app code to serverless environments, avoid configuring bundlers, reduce boot-time and I/O overhead, and get a compiled-language-like experience for Node programs.

### 采用历史

GitHub API data retrieved on 2026-07-01 showed 9,817 stars and 316 forks. The npm downloads API reported 3,712,545 downloads for @vercel/ncc and 56,253 downloads for legacy @zeit/ncc during 2026-05-30 through 2026-06-28.

GitHub's own documentation for creating JavaScript actions names @vercel/ncc alongside Rollup as a way to combine action code and dependencies into one file for distribution, which helped make ncc a common packaging tool in the GitHub Actions ecosystem.

### 使用方式

The standard workflow is ncc build input.js -o dist, producing a compact dist/index.js. Users add flags for minification, source maps, externals, asset builds, TypeScript transpilation, target level, V8 cache output, or license file generation as needed.

Package nerds especially use ncc for JavaScript GitHub Actions and serverless-ish deployment artifacts: commit or publish a small generated dist file instead of vendoring node_modules, while still keeping dependency resolution close to normal Node.js semantics.

### 为什么软件包爱好者会关心

ncc became the boring answer to 'I need one Node file, not a bundler project.' Its constraint is also its appeal: it targets Node programs, not browser apps, so the command stays small and packaging-oriented.

### 时间线

- 2018-11-13: vercel/ncc repository created and @zeit/ncc package created on npm.
- 2020-08-12: @vercel/ncc package created on npm.
- 2024-11-15: 0.38.3 release published.
- 2026-06-29: 0.44.1 release published.
- 2026-07-01: Homebrew Formulae reported stable version 0.44.1.

### Related projects

- @zeit/ncc
- GitHub Actions JavaScript actions
- webpack asset relocator

### 来源

- <https://api.github.com/repos/vercel/ncc>
- <https://api.github.com/repos/vercel/ncc/releases>
- <https://api.npmjs.org/downloads/point/last-month/%40vercel/ncc>
- <https://api.npmjs.org/downloads/point/last-month/%40zeit/ncc>
- <https://docs.github.com/actions/tutorials/creating-a-javascript-action>
- <https://formulae.brew.sh/api/formula/ncc.json>
- <https://github.com/vercel/ncc>
- <https://raw.githubusercontent.com/vercel/ncc/main/readme.md>
- <https://registry.npmjs.org/%40vercel/ncc>
- <https://registry.npmjs.org/%40zeit/ncc>


## 安全说明

narrow executable package without higher-risk signals.

- **Geiger 风险:** 绿色 / 低
- narrow executable package without higher-risk signals


## Combined YAML source

View the package source record on GitHub. [combined/ncc.yml](https://github.com/mxcl/pkgdb/blob/main/combined/ncc.yml)


## 来源

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph