sandboxedjs 0.1.25 → 0.1.26

package/README.md

@@ -597,6 +597,16 @@ await box.exec("ls -la /");      // shell + coreutils
 await box.exec("node app/index.js");
 ```
 
+**Verified in a browser.** Booted under Vite 8, a container starts in the page and the shell,
+coreutils, virtual filesystem and Node runtime all work:
+
+```
+$ uname -a               Linux sandbox 5.10.0 (sandboxedjs@sandbox) … x86_64 GNU/Linux
+$ ls -la /               the full FHS tree
+$ node -p process.version  v22.12.0
+$ cat /etc/os-release    SandboxedJS 1.0 (sandbox)
+```
+
 **Not done — three things stand between this and a browser IDE.**
 
 - *A service worker.* A preview iframe needs a real URL, and giving it one means a worker on your
@@ -613,6 +623,10 @@ await box.exec("node app/index.js");
   nothing to borrow, so anything routed through esbuild fails until esbuild-wasm runs *inside*
   the sandbox.
 
+Vite prints two warnings about `util` being externalized. They come from `readable-stream`, which
+declares `"util": false` for browsers and falls back on its own; nothing in this package imports
+it.
+
 Everything else is already browser-shaped. Nothing in the runtime imports a `node:` builtin except
 through an explicitly Node-only path that returns `null` elsewhere, compression and hashing pick
 their implementation at call time, and the module engine, volume, HTTP stack and npm installer are