vercel /vercel

Develop. Preview. Ship.

★ 16,602⑂ 3,916👁 238⑃ 10,781● 2,880▤ 4,903
TypeScriptApache-2.0Created 2016-09-09vercel.com
下载:@vercel/[email protected]@vercel/[email protected] ↓2.11.132026-07-30
+8
日增长
16,602
stars
3,916
forks
238
watchers
10,781
prs
2,880
issues
4,903
releases

README

Vercel
  



  Develop. Preview. Ship.



  Documentation ·
  Changelog ·
  Templates ·
  CLI



 Vercel

Vercel’s AI Cloud is a unified platform for building modern applications, giving teams the tools to be flexible, move fast, and stay secure while focusing on their products instead of infrastructure.

 Deploy

Get started by importing a project, choosing a template, or using the Vercel CLI. Then, git push to deploy.

 Native CLI binaries

The standard npm installation remains unchanged:

bash
npm i -g vercel


Native CLI binaries are distributed separately and do not affect the vercel npm package. To opt into the native binary and replace existing global vercel and vc commands, install the native package explicitly:

bash
npm i -g @vercel/vc-native --force


The --force flag allows npm to replace existing global vercel and vc bin links. Users who do not install @vercel/vc-native continue using the regular Node.js-based CLI from npm i -g vercel.

Platform-specific packages are also available for direct installation when a specific binary is needed:

bash
npm i -g @vercel/vc-native-darwin-x64 --force


 Documentation

For details on how to use Vercel, check out our documentation.

 Contributing

This project uses pnpm to install dependencies and run scripts.

You can use the vercel script to run local changes as if you were invoking Vercel CLI. For example, vercel deploy --cwd=/path/to/project could be run with local changes with pnpm vercel deploy --cwd=/path/to/project.

When contributing to this repository, please first discuss the change you wish to make via Vercel Community with the owners of this repository before submitting a Pull Request.

Please read our Code of Conduct and follow it in all your interactions with the project.

 Local development

This project is configured in a monorepo, where one repository contains multiple npm packages. Dependencies are installed and managed with pnpm, not npm CLI.

To get started, execute the following:

bash
git clone https://github.com/vercel/vercel
cd vercel
corepack enable
pnpm install
pnpm build
pnpm lint
pnpm test-unit


Make sure all the tests pass before making changes.

 Running Vercel CLI Changes

You can use pnpm vercel from the cli package to invoke Vercel CLI with local changes:

bash
cd ./packages/cli
pnpm vercel 


See CLI Local Development for more details.

 Verifying your change

Once you are done with your changes (we even suggest doing it along the way), make sure all the tests still pass by running:

bash
pnpm test-unit


from the root of the project.

If any test fails, make sure to fix it along with your changes. See Interpreting test errors for more information about how the tests are executed, especially the integration tests.

 Reproducing affected builds and type-checks

CI compares the pull request head with the base and head commits recorded by GitHub. To inspect the same affected Turborepo task plan locally, commit your changes, check out the pull request head, and set

Top issues

Discussions

Latest release

@vercel/[email protected] @vercel/[email protected] 2026-07-30
Patch Changes

- a69c714: Propagate per-function maxConcurrency configuration into build outputs and keep every configured Next.js route in its own Lambda group, including routes with the same limit.
  - @vercel/[email protected]

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON