dev-prune-windows-x86 1.7.0 → 1.8.0

package/README.md

@@ -119,6 +119,7 @@ problem.
 ### From a package manager
 
 ```bash
+npm install -g dev-prune      # or: npx dev-prune status
 uv tool install dev-prune     # or: uvx dev-prune status
 pipx install dev-prune
 pip install dev-prune
@@ -126,9 +127,15 @@ cargo binstall dev-prune      # fetches the prebuilt release archive
 cargo install dev-prune       # builds from source, needs Rust 1.88+
 ```
 
-The PyPI packages **contain the binary** — there is no download step at install time,
-so they work behind a registry mirror and offline. Everything but `cargo install` ships
-a prebuilt executable.
+The npm and PyPI packages **contain the binary** — there is no download step at install
+time, so they work under `npm ci --ignore-scripts`, behind a registry mirror and offline.
+Everything but `cargo install` ships a prebuilt executable.
+
+npm delivers it the way esbuild and Biome do: one small `dev-prune` package that lists
+seven platform packages as optional dependencies, of which npm installs exactly the one
+matching your machine. That is why there is no download step to block. Windows works from
+1.8.0 onwards — earlier versions installed and then reported no binary to run, so a
+machine still holding `dev-prune@1.7.0` needs `npm install -g dev-prune@latest`.
 
 crates.io stores source and nothing else, so `cargo install` has no binary to fetch and
 always compiles. [`cargo binstall`](https://github.com/cargo-bins/cargo-binstall) is the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dev-prune-windows-x86",
-  "version": "1.7.0",
+  "version": "1.8.0",
   "description": "Prebuilt dev-prune binary for windows x86. Installed automatically by the 'dev-prune' package; not meant to be depended on directly.",
   "os": ["win32"],
   "cpu": ["ia32"],