@nickderobertis/allowlister-remote-plugin 0.10.0 → 0.12.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +13 -10
  2. package/package.json +4 -4
package/README.md CHANGED
@@ -1,26 +1,29 @@
1
1
  # @nickderobertis/allowlister-remote-plugin
2
2
 
3
- Installs the native `allowlister-remote-plugin` binary used by allowlister to
4
- send dynamic approval requests to the remote approval PWA.
3
+ Installs the native `allowlister-remote-plugin` and `allowlister-remote-daemon`
4
+ binaries used by allowlister to send dynamic approval requests to the remote
5
+ approval PWA. The plugin hands each request to the daemon (auto-started, one per
6
+ host), which holds a single WebSocket to the broker.
5
7
 
6
8
  ```console
7
9
  npm install -g @nickderobertis/allowlister-remote-plugin
8
10
  allowlister-remote-plugin --version
9
11
  ```
10
12
 
11
- Configure allowlister to run `allowlister-remote-plugin --server-url <url>` as a
12
- dynamic plugin command.
13
+ Configure allowlister to run `allowlister-remote-plugin --broker-url <ws-url>` as
14
+ a dynamic plugin command.
13
15
 
14
16
  ## How it installs
15
17
 
16
- The native binary for each platform ships in its own package
18
+ The native binaries for each platform ship in its own package
17
19
  (`@nickderobertis/allowlister-remote-plugin-darwin-arm64`, `-linux-x64`,
18
20
  `-win32-x64`), declared here as optional dependencies and gated by `os`/`cpu`, so
19
- npm downloads only the one matching your machine. On install, a small step links
20
- that native binary directly onto the `allowlister-remote-plugin` command, so the
21
- command on your `PATH` **is** the Rust executable no Node process is started per
22
- invocation. This matters because allowlister may call the plugin hundreds of
23
- times in a single agent session.
21
+ npm downloads only the one matching your machine. Each carries both the plugin
22
+ and the `allowlister-remote-daemon` it auto-starts. On install, a small step links
23
+ the native plugin directly onto the `allowlister-remote-plugin` command (with the
24
+ daemon as its sibling), so the command on your `PATH` **is** the Rust executable
25
+ no Node process is started per invocation. This matters because allowlister may
26
+ call the plugin hundreds of times in a single agent session.
24
27
 
25
28
  A JS launcher is shipped as a fallback and is used only when the in-place link
26
29
  cannot be made — on Windows (where npm's command shims require it) or when
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nickderobertis/allowlister-remote-plugin",
3
- "version": "0.10.0",
3
+ "version": "0.12.0",
4
4
  "description": "npm installer for the allowlister remote dynamic approval plugin",
5
5
  "type": "module",
6
6
  "license": "UNLICENSED",
@@ -28,8 +28,8 @@
28
28
  "node": ">=20"
29
29
  },
30
30
  "optionalDependencies": {
31
- "@nickderobertis/allowlister-remote-plugin-darwin-arm64": "0.10.0",
32
- "@nickderobertis/allowlister-remote-plugin-linux-x64": "0.10.0",
33
- "@nickderobertis/allowlister-remote-plugin-win32-x64": "0.10.0"
31
+ "@nickderobertis/allowlister-remote-plugin-darwin-arm64": "0.12.0",
32
+ "@nickderobertis/allowlister-remote-plugin-linux-x64": "0.12.0",
33
+ "@nickderobertis/allowlister-remote-plugin-win32-x64": "0.12.0"
34
34
  }
35
35
  }