metavr
v0.0.2
Published
Placeholder to reserve the 'metavr' name. Will be replaced by the contents of @meta-quest/hzdb (Horizon Debug Bridge) published under the new name 'metavr'.
Readme
metavr
Temporary placeholder. This 0.0.1 release only exists to reserve the
metavrname on npm and confirm the registry's typosquat/abuse checks don't block it. It will be replaced by the contents of@meta-quest/hzdb(Horizon Debug Bridge) published under the new namemetavr.
What it does
Thin pass-through to @meta-quest/hzdb: bin.js resolves the platform-specific
binary and execs it.
| Platform | Binary package |
|----------|----------------|
| darwin-arm64 | @meta-quest/hzdb-darwin-arm64 |
| darwin-x64 | @meta-quest/hzdb-darwin-x64 |
| win32-x64 | @meta-quest/hzdb-win32-x64 |
Only the binary for the current platform is fetched (declared as
optionalDependencies).
Binary resolution (self-healing)
Because optionalDependencies are best-effort — npm silently skips them under
omit=optional, the cross-platform lockfile bug, transient failures, or private
mirrors that don't carry them — download.js adds a fallback so the CLI still
works. Resolution order:
- Installed optionalDependency — the normal path. No network.
- Local cache —
~/.metavr/binaries/<pkg>/<version>/<bin>. - On-demand download — fetch the exact-version tarball from the configured
npm registry (
npm_config_registry), verify its publishedsha512integrity before use, extract the binary, and cache it.postinstall.jsalso pre-warms this at install time (best-effort, never fails the install).
Set METAVR_SKIP_DOWNLOAD=1 to disable the network fallback (e.g. airgapped
builds); resolution then stops after step 2 with a clear error.
Usage
npm install -g metavr
metavr --help