toiljs 0.0.61 → 0.0.63

package/test/ssr-template.test.tsx

@@ -356,8 +356,12 @@ describe('ssr build orchestration', () => {
 
         const tmpl = art.tmpl.toString('utf8');
         // Full document with the layout + page scaffold spliced into #root, holes removed.
+        // `<!--$-->` / `<!--/$-->` are the Suspense dehydration markers `assembleRouteElement`
+        // emits by wrapping each layout AND the route in `Suspense` (mirroring the client
+        // Router), so `hydrateRoot` can align its Suspense boundaries. The `<!-- -->` after `@`
+        // is React's text-boundary marker for the `username` hole; the hole text is stripped.
         expect(tmpl).toContain(
-            '<div id="root"><div class="app"><main><h1>@</h1><div></div><ul></ul></main></div></div>',
+            '<div id="root"><!--$--><div class="app"><!--$--><main><h1>@<!-- --></h1><div></div><ul></ul></main><!--/$--></div><!--/$--></div>',
         );
         expect(tmpl).toContain('<template id="__toil_ssr"></template>');
         expect(tmpl).toContain('/assets/app-abc123.js'); // bootstrap script preserved

package/examples/basic/server/streams/Echo.ts

@@ -1,49 +0,0 @@
-/**
- * A `@stream` protocol handler mounted at `/echo`, running as a RESIDENT wasm box
- * per WebTransport connection on the Toil edge - distributed across the eligible
- * L2/L3 nodes and pinned to ONE worker for the connection's lifetime via QUIC
- * connection-id steering.
- *
- * The defining property of a `@stream` (vs a `@rest` handler): the box is
- * RESIDENT, so instance state PERSISTS across events on the same connection. Here
- * `count` survives every `@message` because the box is never reset between events
- * - unlike a `@rest` handler, which is fresh per request. On the client:
- *
- *   const stream = await Server.STREAM.echo.connect();
- *   stream.send(new TextEncoder().encode('hi'));
- *
- * Lifecycle hooks: `@connect` (open), `@message` (an inbound frame), `@close`
- * (graceful close), `@disconnect` (abrupt transport loss).
- *
- * NOTE: reading the inbound frame and replying is the NEXT increment (the
- * `StreamPacket` / `StreamOutbound` message bridge). The intended shape is:
- *
- *   @message reply(packet: StreamPacket): StreamOutbound {
- *     return StreamOutbound.reply(packet.bytes());   // echo the bytes back
- *   }
- *
- * Until that lands, the hooks run on the connection lifecycle; this example counts
- * frames to demonstrate that the resident box keeps state across them.
- */
-@stream('echo')
-class Echo {
-    // Resident per-connection state: survives across events (ResetMode::None).
-    private count: i32 = 0;
-
-    @connect
-    onConnect(): void {
-        // A fresh connection: its dedicated box starts the counter at 0.
-        this.count = 0;
-    }
-
-    @message
-    onMessage(): void {
-        // Persists across frames because the box is resident, not reset per event.
-        this.count = this.count + 1;
-    }
-
-    @close
-    onClose(): void {
-        // Graceful close: the per-connection box is torn down after this hook.
-    }
-}