@poe-platform/safe-js 0.1.802 → 0.1.804

package/README.md

@@ -8,7 +8,7 @@ built-ins. It is suitable for capability-controlled scripts and agent workflows.
 Complete ECMAScript conformance has not been established; see
 [development status](#development-status) and [meaningful limitations](#meaningful-limitations).
 
-Under `workerd` and `browser` conditions, the standalone root and `/core` exports select the portable interpreter with `makeFsModule`, `makeEnvModule`, `makeTimeModule`, `makeFailModule`, `makeMetricModule`, and `makeHarnessModule`. The `/modules/fs` entry is also portable; supply a filesystem adapter for host file access.
+Under `workerd` and `browser` conditions, the standalone root and `/core` exports select the portable interpreter with parsing (`parse`, `parseModule`, `parseSourceModule`), checkpoints (`dump`, `restore`), sandbox copy helpers, error classes, `declareHostOperation`, `makeFsModule`, `makeEnvModule`, `makeTimeModule`, `makeFailModule`, `makeMetricModule`, and `makeHarnessModule`. The `/modules/fs` entry is also portable; supply a filesystem adapter for host file access.
 
 ## Quickstart
 
@@ -38,7 +38,7 @@ console.log(result.returnValue);
 
 `run()` takes source text, not a file path. Success returns `ok`, `returnValue`, `snapshot`, and `stats`. Handle both an `ok: false` result and a rejected promise: parsing, budget exhaustion, cancellation, and some execution failures can reject. Top-level `await` in this example lets rejections reach Node.
 
-`@poe-platform/safe-js/core` exposes `run`, `createRealm`, `defineExtension`, `lint`, `Budget`, and replayable-random helpers for Node.js. In Workers, the `@poe-platform/safe-js` root selects `/workerd`: it exports the portable core API plus `declareHostOperation` without requiring `nodejs_compat`, including the runtime hooks needed by Safe Bash's `nodeCommands()`. The `/core` and `/modules/fs` workspace entries also bundle with the `workerd` or `browser` condition without Node built-ins. Supply a `@poe-platform/safe-fs/core` adapter for filesystem capabilities; `createRootedSourceResolver(root, adapter)` grants portable source imports. File snapshots, migrations, harnesses, and file-running helpers also accept an `adapter`. The shared filesystem lives in `@poe-platform/safe-fs`, with a portable `/core` entry. Existing `@poe-platform/safe-js/fs`, `/fs/core`, and `/fs/node` imports re-export it. Legacy `poe-code/safe-js` imports remain available through the CLI package but use a separate runtime; keep factories and errors within one import family.
+`@poe-platform/safe-js/core` exposes `run`, `createRealm`, `defineExtension`, `lint`, `Budget`, and replayable-random helpers for Node.js. In Workers, the `@poe-platform/safe-js` root selects `/workerd`: it exports the portable core API plus `declareHostOperation` without requiring `nodejs_compat`, including the runtime hooks needed by Safe Bash's `nodeCommands()`. The `/core` and `/modules/fs` workspace entries also bundle with the `workerd` or `browser` condition without Node built-ins. Supply a `@poe-platform/safe-fs/core` adapter for filesystem capabilities; `createRootedSourceResolver(root, adapter)` grants portable source imports. File snapshots, migrations, harnesses, and file-running helpers also accept an `adapter`. The root export selects the portable API under `workerd`, `worker`, and `browser` conditions. `makeEnvModule` uses explicit allowed values when supplied and returns `undefined` for missing host variables; `makeLogModule` writes JSON records through `console.log` when writable stdout is unavailable. The shared filesystem lives in `@poe-platform/safe-fs`, with a portable `/core` entry. Existing `@poe-platform/safe-js/fs`, `/fs/core`, and `/fs/node` imports re-export it. Legacy `poe-code/safe-js` imports remain available through the CLI package but use a separate runtime; keep factories and errors within one import family.
 
 ## Supported features
 
@@ -462,7 +462,7 @@ For one-shot use, `run(source, { extensions, grants, ... })` accepts the same re
 
 `JSON.parse` checks both parse paths before building native objects: input work counts toward steps and deadlines, array lengths and object member counts use `arrayLength`, and nesting uses `maxCallDepth` only when explicitly configured. Parsing requires room for a conservative temporary allocation bound of `16 * text.length + 8` data units alongside existing data; whitespace and duplicate keys count toward this bound.
 
-There are no runtime environment variables to set. `makeEnvModule({ allow, values? })` grants reads of names in `allow`; `values` supplies an explicit string map instead of reading the host's `process.env`. Hosts without `process.env` have no ambient values; pass Worker bindings through `values`. Disallowed reads throw `EnvAccessError`; allowed but unset names return `undefined`. Agent and MCP integrations may require their own credentials.
+There are no runtime environment variables to set. `makeEnvModule({ allow, values? })` grants reads of names in `allow`; `values` supplies an explicit string map instead of reading the host's `process.env`. Portable hosts never read ambient environment values, including with `nodejs_compat`; pass Worker bindings through `values`. Disallowed reads throw `EnvAccessError`; allowed but unset names return `undefined`. Agent and MCP integrations may require their own credentials.
 
 <details>
 <summary>Linting, parsing, and value conversion</summary>
@@ -479,7 +479,7 @@ There are no runtime environment variables to set. `makeEnvModule({ allow, value
 | `largeLiteralThreshold` | Threshold for large-literal diagnostics. |
 | `fix`, `fixRanges` | Apply available fixes, optionally restricted to source ranges. |
 
-`parse(source, filename?)` parses a single statement/expression; `parseModule(source, filename?)` parses a harness module. `parseSourceModule(source, filename?)` uses the same built-in parser for ECMAScript source modules and returns executable syntax plus import/export metadata. Source-module execution uses `run(source, { sourceType: "module", sourceResolver })`; the resolver explicitly grants each imported source. `formatInterpreterError(error, { source?, filename?, hostCallName?, maxMessageLength? })` formats an error; `(source, diagnostic)` is also supported.
+`parse(source, filename?)` parses a single statement/expression; `parseModule(source, filename?)` parses a harness module. `parseSourceModule(source, filename?)` uses the same built-in parser for ECMAScript source modules and returns executable syntax plus import/export metadata. Source-module execution uses `run(source, { sourceType: "module", sourceResolver })`; the resolver explicitly grants each imported source. `formatInterpreterError(error, { source?, filename?, hostCallName?, maxMessageLength?, maxCauseDepth? })` formats an error; `(source, diagnostic)` is also supported. Messages and cause chains are unlimited by default; set `maxMessageLength` or `maxCauseDepth` to opt into truncation. Circular cause chains always stop.
 Diagnostic module parsing retains missing-`async` forms so lint can report and
 autofix them. Executable parsing and restored-source compilation reject `await`
 inside non-async functions, including nested functions and template substitutions.

package/dist/safe-js/bundled-yaml/LICENSE

@@ -0,0 +1,13 @@
+Copyright Eemeli Aro <eemeli@gmail.com>
+
+Permission to use, copy, modify, and/or distribute this software for any purpose
+with or without fee is hereby granted, provided that the above copyright notice
+and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
+REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
+FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
+INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS
+OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
+TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF
+THIS SOFTWARE.