wvb upload
Pack, hash, sign, and upload a bundle to the configured remote, with an optional deploy step.
wvb upload publishes a bundle to your remote server. By default it runs the full pipeline in order — pack, then integrity, then signature, then upload — so a single command turns your built assets into a signed, integrity-checked bundle on the remote. The upload step requires remote.uploader in your config; the optional deploy step at the end also requires remote.deployer.
wvb upload # uses config defaults
wvb upload app --version 1.2.0
wvb upload app --version 1.2.0 --deploy --channel beta
wvb upload --no-pack --file ./build/app.wvb --forceOptions
| Option | Aliases | Default | Description |
|---|---|---|---|
BUNDLE | — | from config / --file name | Bundle name. Positional argument. |
--version | -V | config or package.json version | Version to publish. |
--file | -F | resolved output path | Path to the .wvb to upload. |
--force | — | false | Overwrite if the version already exists on the remote. |
--deploy | — | false | Deploy the version after uploading. |
--channel | — | — | Channel to deploy to. Used with --deploy. |
--pack | -P | true | Pack from pack.srcDir before uploading. Pass --no-pack to skip. |
--skip-integrity | — | false | Skip computing the integrity hash. |
--skip-signature | — | false | Skip signing the bundle. |
--config | -C | config auto-discovery | Path to the config file. |
--cwd | — | process.cwd() | Working directory for resolving paths. |
The version is the --version (-V) flag, not a positional argument. The first positional is the
bundle name. --deploy defaults to false, so an upload publishes the version without making it
current — clients keep receiving the previously deployed version until you deploy this one.
Pipeline
wvb upload runs these stages in order:
- Pack — packs
pack.srcDirinto a.wvbarchive. Skip with--no-packand pass an existing bundle through--file. - Integrity — computes the integrity hash. Skip with
--skip-integrity. - Signature — signs the bundle. Skip with
--skip-signature. - Upload — sends the bundle to the remote through
remote.uploader. - Deploy (optional) — runs only with
--deploy, marking the uploaded version current throughremote.deployer.
On success the command prints the bundle endpoint.
Requirements
remote.uploadermust be configured for the upload step. See Remote, integrity & signature config.remote.deployeris additionally required when you pass--deploy. To deploy a version separately later, usewvb deploy.
For the publishing model and a local-testing walkthrough, see Building a remote.