From 824cc5d0c1743e71f240e3f42fc8cbe0a94eb6ca Mon Sep 17 00:00:00 2001 From: Sylvestre Ledru Date: Sat, 4 Apr 2026 12:59:52 +0200 Subject: [PATCH] Docs: update how-it-works to reflect removal of JS fallback --- content/playground-how-it-works.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/playground-how-it-works.md b/content/playground-how-it-works.md index 836b79e2d..80b1594a2 100644 --- a/content/playground-how-it-works.md +++ b/content/playground-how-it-works.md @@ -119,7 +119,7 @@ flowchart TB - The WASM binary is compiled with `WebAssembly.compileStreaming()` for best performance, with a fallback to `arrayBuffer()` if the server doesn't set `application/wasm` content-type. -- While WASM loads, a JavaScript fallback provides basic implementations of `echo`, `cat`, `seq`, `factor`, `wc`, `ls`, and `basename`. +- Commands are disabled until the WASM binary finishes loading. The terminal shows a loading message and a prompt appears once it's ready. - The `SharedArrayBuffer` polyfill stub prevents `ReferenceError` in browsers without cross-origin isolation headers. ## Command Parsing & Pipes