Filesystem
A writable, watchable POSIX-style project filesystem.
Browser-native Node.js runtime
Filesystem, shell, npm packages, and HTTP servers. No backend required.
Real Node.js programs. Real npm packages. No framework-specific simulation.
npm install @scelar/nodepodThat is exactly why it matters.
There is no Vite emulation layer inside the runtime, no Next.js compatibility mode, and no list of blessed frameworks. Nodepod implements the Node primitives they expect: files, processes, modules, packages, workers, and HTTP.
When Vite 8 or a Next.js app boots, it is their code executing inside Nodepod. The framework is not recreated or hardcoded into the runtime. It simply runs.
$ npm install vite@8
$ npx vite --host 0.0.0.0
VITE v8 ready
Local: http://localhost:5173/Representative hosted workflow. The live Pages demo below is intentionally offline and does not expose HTTP preview.
Start an ephemeral Node.js project in this tab. Nothing is uploaded, saved, or installed on your machine.
This Pages demo runs without a service worker or shared memory. HTTP preview and the complete hosted feature set are intentionally disabled.
Runtime code loads only when you ask for it.
Nodepod could not start in this browser.
A writable, watchable POSIX-style project filesystem.
Scripts, CLIs, child processes, and worker threads.
npm resolution, CommonJS, ESM, and native-feeling imports.
Node-compatible HTTP servers connected back to the host app.
Made for browser IDEs, coding playgrounds, interactive documentation, technical interviews, and local-first developer tools.
A host application boots Nodepod. Workers execute programs against an in-memory filesystem. Node-compatible modules provide the environment existing tools already understand.
Read how it worksNodepod is source-available under the MIT License with the Commons Clause. The LICENSE file is authoritative.
Sponsorship will support compatibility work, documentation, and the long tail of Node APIs.
Sponsorship details