mirror of
https://github.com/LukeHagar/vercel.git
synced 2025-12-07 04:22:04 +00:00
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/python@4.3.0 ### Minor Changes - support newer python versions ([#11675](https://github.com/vercel/vercel/pull/11675)) ## @vercel/build-utils@8.2.1 ### Patch Changes - [node] update node@16 deprecation day ([#11671](https://github.com/vercel/vercel/pull/11671)) ## vercel@34.2.4 ### Patch Changes - Updated dependencies \[[`3eb9d8c89`](3eb9d8c892), [`83741a0eb`](83741a0eb9)]: - @vercel/python@4.3.0 - @vercel/build-utils@8.2.1 - @vercel/node@3.1.6 - @vercel/static-build@2.5.10 ## @vercel/client@13.2.8 ### Patch Changes - Updated dependencies \[[`83741a0eb`](83741a0eb9)]: - @vercel/build-utils@8.2.1 ## @vercel/gatsby-plugin-vercel-builder@2.0.32 ### Patch Changes - Updated dependencies \[[`83741a0eb`](83741a0eb9)]: - @vercel/build-utils@8.2.1 ## @vercel/node@3.1.6 ### Patch Changes - Updated dependencies \[[`83741a0eb`](83741a0eb9)]: - @vercel/build-utils@8.2.1 ## @vercel/static-build@2.5.10 ### Patch Changes - Updated dependencies \[]: - @vercel/gatsby-plugin-vercel-builder@2.0.32 ## @vercel-internals/types@1.0.37 ### Patch Changes - Updated dependencies \[[`83741a0eb`](83741a0eb9)]: - @vercel/build-utils@8.2.1 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@vercel/client
The official Node.js client for deploying to Vercel.
Usage
Firstly, install the package:
npm install @vercel/client
Next, load it:
const { createDeployment } = require('@vercel/client');
Then call inside a for...of loop to follow the progress with the following arguments:
<path>- a directory path / file path / array of file paths (must be on the same level)<options>- An object containingtoken, an optionalteamIdand anyvercel.json-valid fields
async function deploy() {
let deployment;
for await (const event of createDeployment({
token: process.env.TOKEN,
path: '/Users/me/Code/myproject',
})) {
if (event.type === 'ready') {
deployment = event.payload;
break;
}
}
return deployment;
}
Full list of events:
[
// File events
'hashes-calculated',
'file-count',
'file-uploaded',
'all-files-uploaded',
// Deployment events
'created',
'building',
'ready',
'alias-assigned',
'warning',
'error',
];
You can also get the events set programmatically:
import { EVENTS } from '@vercel/client';