Skip to content

fix(npm): lazy install ignores npm shims; publish hanzo alongside @hanzo/cli - #32

Merged
zeekay merged 1 commit into
mainfrom
fix/npm-lazy-shims
Nov 4, 2026
Merged

zeekay merged 1 commit into
mainfrom
fix/npm-lazy-shims

Conversation

@zeekay

@zeekay zeekay commented Nov 4, 2026

Copy link
Copy Markdown
Member

Verified end-to-end: npm i -g --ignore-scripts of both tarballs, then hanzo --version, hanzo-mcp --version, hanzo-dev --version each lazily fetched + ran their native binary; install.js engine fetched hanzo-engine 1.7.92.

…ckout

- `hasTool` no longer counts npm's global shims (symlinks to hanzo.js) as the
  tool, so `hanzo-mcp`/`hanzo-dev` installed via `npm i -g hanzo` actually
  fetch their native binary on first run. The binary the launcher execs must
  be local; companions only need to resolve on PATH.
- Works with npm 11+'s blocked install scripts: the CLI binary itself is
  fetched lazily on first run when postinstall never ran.
- Label a fallback-to-latest download honestly.
- publish-npm.yml checks out hanzo-js/hanzo with actions/checkout (a bare
  git clone prompted for credentials on the runner).
@zeekay zeekay self-assigned this Nov 4, 2026
@zeekay
zeekay merged commit 7989129 into main Nov 4, 2026
@zeekay
zeekay deleted the fix/npm-lazy-shims branch November 4, 2026 03:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant