kern-sandbox 0.2.5 → 0.2.6

package/README.md

@@ -28,8 +28,11 @@ const r = await kern.runCode("print(sum(range(100)))");
 console.log(r.stdout, r.success); // "4950\n" true
 ```
 
-TypeScript types ship in the package. `Buffer` is in the public surface, so a TypeScript consumer also
-needs `@types/node`; without it `tsc` reports `Cannot find name 'Buffer'` and says what to install.
+TypeScript types ship in the package. `Buffer` is in the public surface, so a TypeScript consumer needs
+`@types/node` **and** a `tsconfig.json` that includes it. MEASURED with `tsc` 7.0.2: without the types,
+8 errors saying `Cannot find name 'Buffer'`; with the types installed but no `tsconfig.json`, the same 8;
+with `{ "compilerOptions": { "types": ["node"] } }`, zero. Installing the package `tsc` names is half the
+remedy, which is worth stating because the error message only hints at the other half.
 
 ```ts
 import { runCode, withSandbox, Sandbox } from "kern-sandbox";

package/index.js

@@ -36,7 +36,7 @@ const crypto = require("crypto");
 const zlib = require("zlib");
 const { spawn, spawnSync } = require("child_process");
 
-const VERSION = "0.2.5";
+const VERSION = "0.2.6";
 
 const DEFAULT_IMAGE = "python:3.12-slim";
 const WORKSPACE = "/workspace"; // where the persistent workspace is mounted inside every box

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kern-sandbox",
-  "version": "0.2.5",
+  "version": "0.2.6",
   "description": "kern is a fast, rootless sandbox and virtual resource runtime for any workload, including untrusted and AI-generated code; kern-sandbox is its Node/TypeScript binding. Run untrusted or agent-generated code (Python/JS/Bash) in a real, kernel-enforced box in single-digit milliseconds, with no cloud, no account and no VM.",
   "keywords": [
     "sandbox",