Files
zapd/npm/package.json
zeekay 937adac37a Publish only on green: the release runs CI first, and reads its tokens from KMS, as 1.1.8
The release calls ci.yml before anything is built: every platform's
tests, Windows included, must pass before the binaries, the wheels or
the crate are made. The crate is published by this workflow with the
KMS CARGO_REGISTRY_TOKEN, and npm with the KMS NPM_TOKEN, both granted
to hanzo-ci, as PyPI already was; crates.io trusted publishing was never
configured for the repository, and the repository's npm secret could
not publish the package. The npm installer fetches the Windows binary.

Claude-Session: https://claude.ai/code/session_01M8RoubcPN71KgJuZ8LdBUL
2026-10-15 04:50:39 -07:00

38 lines
785 B
JSON

{
"name": "@zap-proto/zapd",
"version": "1.1.2",
"description": "The ZAP router's operator tool: `zapd pair` prints the browser pairing code, `zapd ls` lists the nodes on this machine's router. Downloads the canonical zap-proto/zapd native binary for your platform.",
"bin": {
"zapd": "bin/zapd.js"
},
"scripts": {
"postinstall": "node install.js"
},
"os": [
"darwin",
"linux",
"win32"
],
"cpu": [
"x64",
"arm64"
],
"files": [
"bin/zapd.js",
"install.js"
],
"repository": {
"type": "git",
"url": "git+https://github.com/zap-proto/zapd.git"
},
"homepage": "https://github.com/zap-proto/zapd",
"keywords": [
"zap",
"zapd",
"router",
"broker",
"rpc"
],
"license": "MIT OR Apache-2.0"
}