wvb builtin
Install builtin webview bundles into your app from a remote or local target.
wvb builtin installs bundles into an output directory so your app can ship them as builtin fallbacks. When the app starts offline, or before it has fetched a newer bundle over the air, it serves these builtin bundles. The command pulls from the source defined by builtin.target in your config, which defaults to a remote target.
The command writes a manifest.json describing the installed set, plus one file per bundle laid out as <name>/<name>_<version>.wvb. For how builtin and remote sources work together, see Bundle sources.
Usage
# Install from the configured target into the default directory
wvb builtin
# Install from a remote endpoint into an explicit directory
wvb builtin --endpoint https://updates.example.com --out .wvb/builtin/bundles
# Filter which bundles get installed
wvb builtin --include 'app*' --exclude 'internal*'
# Install into the detected Android module
wvb builtin --android
# Dry run: report what would be installed without writing
wvb builtin --no-writeOptions
| Option | Aliases | Default | Description |
|---|---|---|---|
--out | -O | .wvb/builtin/bundles | Output directory. A mobile preset changes this to the platform module directory. |
--endpoint | -E | remote.endpoint | Remote endpoint to pull from. Remote target only. |
--channel | — | — | Release channel to install from. Remote target only. |
--include | — | — | Glob include patterns over the target bundles. Repeatable. |
--exclude | — | — | Glob exclude patterns over the target bundles. Repeatable. |
--clean | — | true | Clear the output directory before installing. Pass --no-clean to keep existing files. |
--concurrency | — | CPU count, capped at 8 | Number of parallel downloads. Remote target only. |
--android | — | — | Mobile preset. Bare auto-detects the app module; --android=<dir> sets it explicitly. |
--ios | — | — | Mobile preset. Bare auto-detects the project; --ios=<dir> sets it explicitly. |
--write | — | true | Write the installed files. Pass --no-write for a dry run. |
--progress | — | true | Show a download progress bar. Remote target only. |
--config | -C | (auto-discovery) | Path to the config file. |
--cwd | — | process.cwd() | Working directory for resolving paths. |
Boolean flags accept --flag, --flag=true|false, and a --no-flag negation, so --no-write and --no-clean turn off the --write and --clean defaults.
Mobile presets
--android and --ios install bundles into a platform project instead of a plain directory. Each can be passed bare to auto-detect the target, or as --android=<dir> / --ios=<dir> to point at an explicit module or project directory. The --ios preset adds a folderReference to Project.swift, which applies to Tuist projects.
--android and --ios in the same run.Notes
- The target type comes from
builtin.targetin your config, a discriminated union ofremoteandlocal. It defaults to a remote target. --endpoint,--channel,--concurrency, and--progressapply to the remote target only.- A successful run writes a
manifest.jsonand one<name>/<name>_<version>.wvbfile per installed bundle.