▲BrowserPod: In-browser full-stack environments for IDEs and Agents via WASM(labs.leaningtech.com)
47 points by apignotti 6 hours ago | 6 comments
▲hk1337 4 hours ago
> Incompatible Browser

> This demo requires a Chromium-based browser (Chrome, Edge, Brave) to function properly.

> Please switch to a compatible browser to experience the full capabilities of BrowserPod.

well, that sucks.

▲apignotti 4 hours ago
We are working on it. Firefox is currently unsupported due to Atomics.waitAsync being not yet enabled by default. Safari on the other hand has some subtle inconsistent behavior at the edge between getters, global variables and `this`.

BrowserPod is intended to work across all browsers, but we are not there yet.

▲irrationalfab 2 hours ago
Very interesting tech. Ephemeral, high-fidelity preview environments that require zero setup are a key enabler. They let you rapidly validate changes within the complete context of a web or mobile app, accelerating feedback loops and cutting friction for minor updates. This also empowers business users to safely implement small, self-contained UI adjustments which is particularly powerful when combined with LLM-driven suggestions.
▲myflash13 3 hours ago
I wonder if this would enable the truly "serverless" application I've been thinking about. Imagine shipping a whole Rails/Laravel/Wordpress app to the user to be run in their browser with sqlite. Technically you would only need a CDN to distribute the app.
▲apignotti 3 hours ago
What you describe is 100% possible. Rails is one of our priorities. PHP is also easy to achieve.
▲mckmk 1 hour ago
Imagine being able to sync that sql database with some sort of cloud storage(s3, google drive, one drive).

Or, even better imagine being able to load your own applications in into your cloud storage and run them in browser remotely.

▲seanw265 3 hours ago
Very cool. I've spent quite some time working on compiling Nodejs for WASIX. Not an easy task.

Would love to see this open sourced at some point.

▲jckahn 3 hours ago
I don't see any indication of this being open source.
▲apignotti 3 hours ago
Indeed, it's not. It's possible we might decide to release the code in the future, but for the time being we are keeping it proprietary.
▲j369 4 hours ago
"In particular, we plan to support React Native environments in 2026." Genuinely curious, what is the benefit or use case of this? I thought react native runs in the web already.
▲apignotti 4 hours ago
React native can indeed target the We. Instead we are referring to running the native build toolchain for react native, which is required to build android apps, in the browser.