@turbobase/isolated-vm-prebuilds 1.1.7 → 1.1.9

package/README.md

@@ -1,39 +1,45 @@
 # @turbobase/isolated-vm-prebuilds
 
 Prebuilt [`isolated-vm`](https://github.com/laverdet/isolated-vm) binaries for the
-platform/ABI pairs upstream does not publish.
+two platforms upstream does not publish, used by the
+[TurboBase CLI](https://www.npmjs.com/package/@turbobase/cli).
 
-You are not meant to install this directly. `turbobase ext extras install` pulls it
-when it needs it and drops the matching binary where `isolated-vm` looks for one.
+**You do not need to install this yourself.** `turbobase ext extras install` pulls
+it when your machine is one of the two platforms that needs it, and drops the
+binary where `isolated-vm` already looks. On every other platform it is never
+fetched.
+
+New to TurboBase? Start at **[docs.turbobase.io](https://docs.turbobase.io/)**.
 
 ## Why it exists
 
-`isolated-vm` compiles against V8 internals, so its prebuilds are **per Node ABI**,
-not just per platform. Version 6.1.2 ships:
+`isolated-vm` compiles against V8 internals, so its prebuilt binaries are **per
+Node ABI**, not just per platform. Version 6.1.2 — the version the CLI pins —
+ships:
 
-| Platform      | abi127 (Node 22) | abi137 (Node 24) |
-| ------------- | ---------------- | ---------------- |
-| darwin-arm64  | ✅               | ✅               |
-| linux-x64     | ✅ glibc + musl  | ✅ glibc + musl  |
-| linux-arm64   | ✅ glibc + musl  | ✅ glibc + musl  |
-| win32-x64     | ✅               | ✅               |
-| **darwin-x64**| ❌               | ❌               |
-| **win32-arm64**| ❌              | ❌               |
+| Platform        | abi127 (Node 22) | abi137 (Node 24) |
+| --------------- | ---------------- | ---------------- |
+| darwin-arm64    | ✅               | ✅               |
+| linux-x64       | ✅ glibc + musl  | ✅ glibc + musl  |
+| linux-arm64     | ✅ glibc + musl  | ✅ glibc + musl  |
+| win32-x64       | ✅               | ✅               |
+| **darwin-x64**  | ❌               | ❌               |
+| **win32-arm64** | ❌               | ❌               |
 
-On the two bottom rows `npm install isolated-vm` falls through to
-`node-gyp rebuild`, which needs Python and a C++ toolchain — on an Intel Mac or a
-Windows-on-ARM machine that is a multi-minute compile at best and a hard failure on
-a stock developer laptop. `turbobase ext test` and `turbobase ext replay` are the
-only commands affected, but they are the two that matter most while authoring.
+On those last two rows `npm install isolated-vm` falls through to `node-gyp
+rebuild`, which needs Python and a C++ toolchain — on a stock Intel MacBook or a
+Windows-on-ARM laptop that is a multi-minute compile at best, and a hard failure
+more often than not.
 
-This package closes those two rows. The binaries are built by the TurboBase release
-workflow's `cli-prebuilds` matrix, from the same pinned `isolated-vm` version the
-CLI declares.
+This package closes those two rows. It matters because `turbobase ext test` and
+`turbobase ext replay` — the commands that run your extension in a
+production-parity sandbox before you ship it — are the ones that load the binary.
 
-## Layout
+## How it is used
 
-Mirrors `isolated-vm`'s own `prebuilds/` tree exactly, so installing is a directory
-merge and `node-gyp-build` resolves the result with no shim:
+`turbobase ext extras install` checks your platform. On `darwin-x64` or
+`win32-arm64` it fetches this package and merges its `prebuilds/` tree into
+`isolated-vm`'s own, where `node-gyp-build` resolves it with no shim:
 
 ```
 prebuilds/darwin-x64/isolated-vm.abi127.node
@@ -42,7 +48,20 @@ prebuilds/win32-arm64/isolated-vm.abi127.node
 prebuilds/win32-arm64/isolated-vm.abi137.node
 ```
 
+Check what you have with `turbobase ext extras status`.
+
+The binaries are compiled by the TurboBase release pipeline from the exact
+`isolated-vm` version the CLI declares, so they cannot drift from the runtime that
+loads them. This package is versioned and published in lockstep with
+`@turbobase/cli`.
+
+## Documentation
+
+- [Sandboxes and testing](https://docs.turbobase.io/extending/sandboxes-and-testing/) — what `ext test` and `ext replay` do
+- [CLI overview](https://docs.turbobase.io/cli/overview/) — installing and using the CLI
+- [docs.turbobase.io](https://docs.turbobase.io/) — the full documentation
+
 ## Licence
 
-The binaries are compiled from `isolated-vm`, which is ISC-licensed. That licence
+The binaries are compiled from `isolated-vm`, which is ISC-licensed; that licence
 travels with them — see `LICENSE`. This package adds no code of its own.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@turbobase/isolated-vm-prebuilds",
-  "version": "1.1.7",
+  "version": "1.1.9",
   "description": "Prebuilt isolated-vm binaries for the platform/ABI pairs upstream does not ship. Consumed by @turbobase/cli's `turbobase ext extras install`; not useful on its own.",
   "license": "ISC",
   "private": false,