wvb extract
Unpack a .wvb archive's files back onto disk to inspect what a bundle contains.
wvb extract reads a .wvb archive and writes its files back onto disk. Use it to inspect what a bundle ships, diff two bundles, or recover the assets that went into one.
Usage
Pass the bundle file to extract. The command writes the unpacked files under an output directory, defaulting to .wvb/<basename without .wvb>.
wvb extract ./build/app.wvb
wvb extract ./build/app.wvb --outdir ./unpacked
wvb extract ./build/app.wvb --outdir ./unpacked --cleanPass --no-write to run the extraction without touching disk, which is useful for verifying that a bundle reads cleanly:
wvb extract ./build/app.wvb --no-writeOptions
| Option | Aliases | Default | Description |
|---|---|---|---|
FILE | — | required | Bundle file to extract. |
--outdir | -O | .wvb/<basename without .wvb> | Destination directory for the unpacked files. |
--clean | — | false | Remove the output directory first if it exists. |
--write | — | true | Pass --no-write to simulate the extract without writing files. |
--cwd | — | process.cwd() | Working directory used to resolve paths. |
wvb extract has no --config flag. It reads only the bundle file you pass and the flags above;
it does not load a wvb.config file. It does accept --cwd to resolve relative paths.
The global --color, --log-level, and --log-verbose flags apply here as they do on every command. Boolean flags accept --flag, --flag=true|false, and a --no-flag negation, so --no-write turns off the default --write behavior.