Builtin bundles

Builtin bundles are the .wvb files you ship inside your Electron package. They are read-only and always present, so your app has something to serve when it starts offline or before it has fetched a newer bundle over the air. Downloaded updates take priority over builtin bundles at runtime — see Bundle sources.

Where builtin bundles land

@wvb/electron reads builtin bundles from source.builtinDir, which defaults to process.resourcesPath/bundles in a packaged app — the resources/bundles directory. Each bundle is laid out as <name>/<name>_<version>.wvb next to a manifest.json.

Install with wvb builtin

wvb builtin installs bundles into an output directory. The source is set by builtin.target in your config: a remote target downloads them from your update server, a local target packs them from local workspaces.

# Install from the configured target into a bundles directory
wvb builtin --out bundles

# Or pull from a remote endpoint explicitly
wvb builtin --endpoint https://updates.example.com --out bundles

Point --out at the directory you ship with your app. See wvb builtin for every flag.

Install at package time

The Forge and Builder integrations install builtin bundles for you during packaging and copy them into the packaged app's resources/bundles, so you never stage .wvb files by hand.