Yarn embeds BrowserPod in its official v6 Playground
Yarn's Playground for version 6 installs a project's dependencies from the npm registry inside the visitor's own browser, with no container provisioned server-side.
BrowserPod has been integrated into Yarn’s official v6 Playground, where it runs the package manager in the visitor’s own browser. Visitors can install a project’s dependencies from the npm registry without a container being provisioned on a remote host.
The integration follows from Yarn 6 being written in Rust. Yarn runs in the Playground as a binary compiled for BrowserPod, so the Playground exercises the same install path developers get on their own machines. Package downloads use BrowserPod’s outbound network access, and the installed dependencies are written to its persistent virtual filesystem. The work happens on the visitor’s machine, so the Playground consumes no server-side compute per session.
BrowserPod 3.0, released on 13 August, added support for Rust. Rather than compile to WASI, which provides for neither thread usage nor the spawning of external programs, Leaning Technologies added a compilation target of its own, wasm32-browserpod-linux-musl. Rust applications compile for it without source changes and retain their threading and process model, filesystem access and network access. ripgrep, starship and jj-vcs have also been verified running unaltered in a browser tab.
The Yarn v6 Playground is publicly accessible. BrowserPod API documentation is published at browserpod.io/docs, and API keys are issued through console.browserpod.io.











