wvb remote
Inspect and test a remote — show the current deployed bundle, list available bundles, and run a local update server.
The wvb remote command group inspects and tests a remote update server. Use it to see which version is currently deployed, list every bundle the remote knows about, and run a local server that mirrors the production HTTP contract so you can exercise the full update loop offline.
It groups three subcommands:
wvb remote current— show the current deployed version and its metadata.wvb remote list— list every bundle available on the remote (aliaswvb remote ls).wvb remote local— start a local update server backed by a directory.
The first two read remote.endpoint from your config by default, so you can drop the --endpoint flag once a remote is configured. For the publishing model and a local-testing walkthrough, see Building a remote.
wvb remote current [BUNDLE]
Show the current deployed version and its metadata for a bundle, without downloading the bundle itself. The output includes the version, ETag, integrity, signature, and last-modified values reported by the remote.
wvb remote current app --endpoint https://updates.example.com
wvb remote current app --channel beta
wvb remote current # uses config defaults| Option | Aliases | Default | Description |
|---|---|---|---|
BUNDLE | — | resolved from config | Bundle name. Falls back to the package name. |
--endpoint | -E | remote.endpoint | Remote endpoint to query. |
--channel | — | — | Release channel. |
--config | -C | config auto-discovery | Path to the config file. |
--cwd | — | process.cwd() | Working directory for resolving paths. |
wvb remote list
List every bundle available on the remote. The command also has the alias wvb remote ls. Output is JSON, so it pipes cleanly into other tools.
wvb remote list --endpoint https://updates.example.com
wvb remote ls --channel beta
wvb remote list | jq '.[].name'| Option | Aliases | Default | Description |
|---|---|---|---|
--endpoint | -E | remote.endpoint | Remote endpoint to query. |
--channel | — | — | Release channel. |
--config | -C | config auto-discovery | Path to the config file. |
--cwd | — | process.cwd() | Working directory for resolving paths. |
wvb remote local
Start a local update server backed by a directory. It implements the same HTTP contract as a production remote, so you can test the full update loop offline before wiring in a hosted provider. The server defaults to serving ~/.wvb/local on port 4313.
wvb remote local # http://localhost:4313, serving ~/.wvb/local
wvb remote local --base-dir ./.wvb/local --port 4313
wvb remote local --allow-other-versions --hostname 0.0.0.0| Option | Aliases | Default | Env | Description |
|---|---|---|---|---|
--base-dir | — | ~/.wvb/local | — | Directory to serve. |
--allow-other-versions | — | false | — | Allow serving versions other than current. |
--hostname | -H | localhost | HOSTNAME | Bind hostname. |
--port | -P | 4313 | PORT | Port to listen on. |
--silent | — | false | — | Disable request logging. |
remote local requires the optional @wvb/remote-local-provider package, which the command
imports on demand. Unlike the other subcommands, it does not read --config or --cwd. The
server stops cleanly on SIGINT or SIGTERM.
By default the local server only serves the version marked current for each bundle. Pass --allow-other-versions to also serve specific older versions, which is useful for testing rollbacks and version pinning.