@dalyem/hopkey 0.1.0-rc.3 → 0.1.0-rc.4

package/README.md

@@ -3,17 +3,17 @@
 The `hop` command of [HopKey](https://github.com/dalyem/HopKey), an end-to-end encrypted vault for SSH hosts and keys. `hop` is a Go program; this package is only a way to get it.
 
 ```
-npm i -g @dalyem/hopkey          # a release
-npm i -g @dalyem/hopkey@next     # the latest prerelease
+npm i -g --allow-scripts=@dalyem/hopkey @dalyem/hopkey          # a release
+npm i -g --allow-scripts=@dalyem/hopkey @dalyem/hopkey@next     # the latest prerelease
 ```
 
 Linux and macOS, on x64 and arm64, with Node 18 or later for the install. The package holds all four builds and downloads nothing when it installs. The server, `hop-server`, is a Docker image: `docker pull ghcr.io/dalyem/hop-server:VERSION`.
 
 ## What `hop` is after the install
 
-The package's postinstall copies the build for your platform over `bin/hop`, so `hop` on your PATH is the native binary: no Node when it runs, and its signals and exit codes are its own. The package contains a small Node launcher at `bin/hop` for installs that skip postinstall scripts (`npm i -g --ignore-scripts`, pnpm and bun by default). The launcher starts `vendor/<os>-<arch>/hop`, passes stdin, stdout and stderr straight through, and exits with hop's exit code, or with hop's signal. It forwards SIGTERM. It does not forward SIGINT or SIGHUP: the terminal already sends those to hop, and a second one makes hop quit at once.
+The package's postinstall copies the build for your platform over `bin/hop`, so `hop` on your PATH is the native binary: no Node when it runs, and its signals and exit codes are its own. The package contains a small Node launcher at `bin/hop` for installs that skip postinstall scripts (npm 12 without `--allow-scripts`, `npm i -g --ignore-scripts`, pnpm and bun by default). The launcher starts `vendor/<os>-<arch>/hop`, passes stdin, stdout and stderr straight through, and exits with hop's exit code, or with hop's signal. It forwards SIGTERM. It does not forward SIGINT or SIGHUP: the terminal already sends those to hop, and a second one makes hop quit at once.
 
-One thing the launcher cannot do: a `nohup hop ...` that should ignore hangups does not, because Node starts its child with default signal handling. If that matters, run the native binary: reinstall without `--ignore-scripts`, or run `vendor/<os>-<arch>/hop` from the package directory (`$(npm root -g)/@dalyem/hopkey`).
+One thing the launcher cannot do: a `nohup hop ...` that should ignore hangups does not, because Node starts its child with default signal handling. If that matters, run the native binary: reinstall with `--allow-scripts=@dalyem/hopkey` and without `--ignore-scripts`, or run `vendor/<os>-<arch>/hop` from the package directory (`$(npm root -g)/@dalyem/hopkey`).
 
 If the postinstall cannot replace `bin/hop` for any reason, it says nothing, the install still succeeds, and the launcher stays.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dalyem/hopkey",
-  "version": "0.1.0-rc.3",
+  "version": "0.1.0-rc.4",
   "description": "HopKey: an end-to-end encrypted vault for SSH hosts and keys (the hop CLI)",
   "keywords": [
     "ssh",