@jevrouter/jevrouter
v0.1.0
Published
Jev-driven local model router — one Choice, three slots, difficulty decides the tier
Maintainers
Readme
jevrouter (npm distribution)
Jev-driven local model router — one Choice, three slots, difficulty decides the tier.
npm install -g @jevrouter/jevrouter
jevrouter serve # the bin name stays `jevrouter`
jevrouter status
jevrouter doctorThis package is a tiny Node launcher (~1KB, no dependencies): npm installs the
matching prebuilt binary as an optionalDependency
(@jevrouter/jevrouter-darwin-arm64 / -darwin-x64 / -linux-x64 / -linux-arm64) and bin/jevrouter.js execs it. The router itself is
native Rust — Node is only the entry point.
Fallbacks
JEVROUTER_BIN=<path>execs an explicit binary (testing).- In a repo checkout without installed platform packages, the launcher falls
back to
target/release/jevrouter.
Publishing (maintainers)
Versions must stay in sync across cli/package.json and all
cli/platforms/*/package.json. Names are scoped (@jevrouter/…): the registry
rejected the unscoped jevrouter as too similar to the existing jev-router;
packages live under the @jevrouter org.
cargo build --release && node cli/scripts/prepare-platforms.mjs
cd cli/platforms/<plat> && npm publish --access public
cd .. && npm publish --access publicCI (.github/workflows/release.yml) builds all four platforms on v* tags,
attaches tarballs to the GitHub release, and publishes to npm when an
NPM_TOKEN secret is configured. Replace OWNER in cli/package.json
with the real GitHub org/user before the first publish.
