@rotifer/playground - npm Package Compare versions

Comparing version 0.10.1 to 0.10.2

CHANGELOG.md

@@ -8,2 +8,10 @@ # Changelog
 
+## [0.10.2](https://github.com/rotifer-protocol/rotifer-playground/compare/v0.10.1...v0.10.2) (2026-08-14)
+
+
+### Bug Fixes
+
+* **release:** stop VS Code-only changes from bumping the npm package ([#166](https://github.com/rotifer-protocol/rotifer-playground/issues/166)) ([ae256d6](https://github.com/rotifer-protocol/rotifer-playground/commit/ae256d6eb939de50d28704d17cfdc5945702eb27))
+* **sandbox:** reject artifacts with an async express() at runtime ([#169](https://github.com/rotifer-protocol/rotifer-playground/issues/169)) ([338322f](https://github.com/rotifer-protocol/rotifer-playground/commit/338322fcc296fe190c4301f5adf09344ed46b5a7))
+
 ## [0.10.1](https://github.com/rotifer-protocol/rotifer-playground/compare/v0.10.0...v0.10.1) (2026-08-11)
@@ -84,29 +92,2 @@
 
-## [Unreleased]
-
-### Added
-
-- **`rotifer doctor`** — checks the TS→WASM toolchain (esbuild / javy) offline and reports
-  per-tool status, the active `npx` path, and the Node prefix running rotifer; exits non-zero
-  when the toolchain is incomplete. Surfaces the preflight from #58 as a standalone command.
-
-### Fixed
-
-- **WASM runtime errors surface the guest's stderr** — when a Native gene traps, the
-  sandbox now appends anything the guest wrote to fd 2 (e.g. the Javy/QuickJS error
-  message) to the failure, instead of returning only an opaque WASM backtrace (R4)
-- **Starter template traps in Native WASM** — `rotifer init` now scaffolds a synchronous
-  `express()`; the previous `async express()` starter compiled fine but trapped in the
-  Javy/QuickJS sandbox with an opaque backtrace (#57)
-- **Async `express()` now rejected at compile time** — `rotifer compile` statically detects
-  `async function express` / Promise-returning signatures and fails with `E0025` and an
-  actionable message, instead of deferring to a runtime trap whose error text was swallowed
-  by the WASM host (#57)
-- **Toolchain failures get a diagnosis instead of `spawnSync npx ETIMEDOUT`** — the TS→WASM
-  pipeline preflights esbuild/javy offline (`npx --no-install`, falling back to the `javy`
-  binary that `javy-cli@3` actually installs) and reports per-tool status, the active `npx`
-  path, and exact install commands; npx no longer hits the npm registry implicitly (#58)
-- **Stale WASM warning on `rotifer run`** — when `index.ts` is newer than `gene.ir.wasm`,
-  run now warns that it is executing stale WASM and suggests recompiling (#58)
-
 ## [0.8.6] - 2026-04-16
@@ -113,0 +94,0 @@

package.json

 {
   "name": "@rotifer/playground",
-  "version": "0.10.1",
+  "version": "0.10.2",
   "description": "Rotifer Protocol Playground — local development environment for gene development, Arena competition, and protocol simulation",
@@ -87,6 +87,6 @@ "license": "Apache-2.0",
     "@rolldown/binding-linux-x64-gnu": "1.1.1",
-    "@rotifer/playground-darwin-arm64": "0.10.1",
-    "@rotifer/playground-darwin-x64": "0.10.1",
-    "@rotifer/playground-linux-x64-gnu": "0.10.1",
-    "@rotifer/playground-win32-x64-msvc": "0.10.1"
+    "@rotifer/playground-darwin-arm64": "0.10.2",
+    "@rotifer/playground-darwin-x64": "0.10.2",
+    "@rotifer/playground-linux-x64-gnu": "0.10.2",
+    "@rotifer/playground-win32-x64-msvc": "0.10.2"
   },
@@ -93,0 +93,0 @@ "engines": {

README.md

@@ -12,3 +12,3 @@ # Rotifer Playground
 
-> **Status:** v0.9.0 — Open Mesh + Economy Foundation: experimental P2P gene propagation (`rotifer network` — run a real libp2p node and propagate gene announcements across a LAN), the v0.9 economy + season system, Hybrid Fidelity genes, and `rotifer doctor`. See [CHANGELOG.md](CHANGELOG.md) for full release history. Automatic peer discovery, internet-wide reach, and L4 Collective Immunity are later milestones — see [Implementation Status](#implementation-status) below.
+> **Status:** v0.10.1 — P2P Reliability on top of v0.9's Open Mesh + Economy Foundation: experimental P2P gene propagation (`rotifer network`) now remembers peers across restarts, and the silent bootstrap failure is gone — nodes ship with no default bootstrap peer, so you pass one explicitly (`rotifer network start -b <multiaddr>`) and there is no public network to join yet. P2P stays off by default (`enabled: false`). Also the v0.9 economy + season system, Hybrid Fidelity genes, and `rotifer doctor`. See [CHANGELOG.md](CHANGELOG.md) for full release history. Automatic peer discovery, internet-wide reach, and L4 Collective Immunity are later milestones — see [Implementation Status](#implementation-status) below.
 
@@ -273,3 +273,3 @@ ---
 
-**Key limitation:** L4 depends on L3's P2P network, which is planned. Full L4 is targeted for v0.9+.
+**Key limitation:** L4 depends on a mature L3 P2P layer. P2P is runnable today but experimental and off by default, and still lacks automatic peer discovery and internet-wide reach. Full L4 is targeted for v1.x.
 
@@ -276,0 +276,0 @@ ---

New alerts

AI-detected potential code anomaly

Supply chain risk

AI has identified unusual behaviors that may pose a security risk.

Found 5 instances

URL strings

Supply chain risk

Package contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.

Fixed alerts

AI-detected potential code anomaly

Supply chain risk

AI has identified unusual behaviors that may pose a security risk.

Found 5 instances

URL strings

Supply chain risk

Package contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.

Worsened metrics

Total package byte prevSize

1029003

-0.06%

No dependency changes