Deployment artifacts
Use void/deploy from Node.js to prepare a built SDK app for a managed platform deploy. You do not need platform credentials.
On this pageBuild deployment artifacts in your own scripts or CI · Check the shape of the artifact · Hand the artifact to a platform
Build the app in managed mode inside its isolated environment.
Now you will run a deploy build that writes an artifact.
VOID_DEPLOY_BUILD=1 VOID_DEPLOY_PROJECT_ID=artifact npm run buildExample output: the build finishes and writes the deploy artifact. Nothing is uploaded.
These values select a platform-compatible build. artifact is a build marker. It is not a project ID or a credential. The target project is chosen during publish approval.
import { prepareDeployArtifact } from 'void/deploy';
const { artifact, assets } = await prepareDeployArtifact('/path/to/app');artifact holds the deploy manifest, content-addressed asset metadata and base64 Worker modules. assets maps asset URL paths to base64 bytes. Do not change this result while you request publish approval.
Preparation only packages existing build output. It does not build, contact a platform, create resources or deploy. It supports Void Cloudflare Worker builds. Node targets, static output, remote data, deploy-time prerendering, Sandbox and Live resources need the normal void deploy workflow.
Run preparation in the same isolated environment as the app build. App config and build plugins run project code. Keep platform credentials on the publishing server only.
