fc7a8bc8ae
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## vercel@34.1.0 ### Minor Changes - Don't propagate legacy env VERCEL_ANALYTICS_ID if @vercel/speed-insights package is detected ([#11305](https://github.com/vercel/vercel/pull/11305)) ### Patch Changes - Replace console.log that communicates to user with client.output methods ([#11353](https://github.com/vercel/vercel/pull/11353)) - [cli] Do not pipe git stderr to user during successful `vc dev` run ([#11450](https://github.com/vercel/vercel/pull/11450)) - fix: Sort default team to the top of the selection list ([#11451](https://github.com/vercel/vercel/pull/11451)) - Updated dependencies \[[`993a60ef7`](993a60ef71), [`949d84ad1`](949d84ad1c), [`5bb96ea07`](5bb96ea072), [`fd8031874`](fd80318743)]: - @vercel/next@4.2.1 ## @vercel/frameworks@3.0.2 ### Patch Changes - Update framework detection to support SolidStart v1 ([#11308](https://github.com/vercel/vercel/pull/11308)) ## @vercel/fs-detectors@5.2.3 ### Patch Changes - Updated dependencies \[[`5f72dc436`](5f72dc4360)]: - @vercel/frameworks@3.0.2 ## @vercel/next@4.2.1 ### Patch Changes - [next] add streaming prerender group for actions ([#11454](https://github.com/vercel/vercel/pull/11454)) - [next] Ensure \_not-found is included properly in app router functions ([#11441](https://github.com/vercel/vercel/pull/11441)) - [next] add .action handling for dynamic routes ([#11461](https://github.com/vercel/vercel/pull/11461)) - [next] Remove un-necessary compressed function size calc/constraint ([#11442](https://github.com/vercel/vercel/pull/11442)) Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Vercel
Develop. Preview. Ship.
Usage
Vercel's frontend cloud gives developers frameworks, workflows, and infrastructure to build a faster, more personalized web.
To install the latest version of Vercel CLI, run this command:
npm i -g vercel
To quickly start a new project, run the following commands:
vercel init # Pick an example project
cd <PROJECT> # Change directory to the new project
vercel # Deploy to the cloud
Finally, connect your Git repository to Vercel and deploy with git push.
Documentation
For details on how to use Vercel CLI, check out our documentation.
Local Development
To develop Vercel CLI, first check out the source code, install dependencies, and build all packages:
git clone https://github.com/vercel/vercel.git
cd vercel
pnpm install
pnpm build
At this point you can make modifications to the CLI source code and test them out locally. The CLI source code is located in the packages/cli directory.
cd packages/cli
pnpm dev <cli-commands...>
From within the packages/cli directory, you can use the "dev" script to quickly execute Vercel CLI from its TypeScript source code directly (without having to manually compile first). For example:
pnpm dev deploy
pnpm dev whoami
pnpm dev login
pnpm dev switch --debug
When you are satisfied with your changes, make a commit and create a pull request!