wasm-workers-server
webcontainer-core
wasm-workers-server | webcontainer-core | |
---|---|---|
5 | 20 | |
501 | 3,622 | |
3.0% | 0.8% | |
8.3 | 2.0 | |
19 days ago | about 1 year ago | |
Rust | ||
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wasm-workers-server
-
Node on Web. Use Nodejs freely in your browser with Linux infrastructure.
"Wasm Workers Server (wws) is an open source tool to develop and run serverless applications server on top of WebAssembly. The applications are composed by multiple modules called workers. Each of these tiny modules is in charge of replying to a specific HTTP endpoint in your application." Wasm Workers Server, "JavaScript Workers based on JavaScript work out of the box with Wasm Workers Server. The server integrates a JavaScript interpreter compiled into a WebAssembly module. Currently, the interpreter we support is quickjs and we are working on adding new ones." JavaScript
- [AskJS] Has anybody implemented and compiled ServiceWorker specification to a standalone executable?
- WASM Workers Server 1.0: adding support for Python and Ruby
- Run your first worker in WebAssembly in 1 minute
-
Show HN: OSS WebAssembly Workers Server Compatible with Cloudflare
Hey, dev here!
Here you have the GitHub and Documentation links:
- https://github.com/vmware-labs/wasm-workers-server/
- https://workers.wasmlabs.dev/
webcontainer-core
-
API Security Academy dedicated to GraphQL security
How does it work? There is no backend whatsoever. The API Security Academy leverages WebContainers, a new technology that allows running full-blown node instances directly in the browser. Each WebContainer contains a live GraphQL application, so you'll not only understand why a vulnerability is risky, but also how to exploit it and, most importantly, how to fix it.
-
Node on Web. Use Nodejs freely in your browser with Linux infrastructure.
StackBlitz made the claim "... run Node.js, entirely inside your browser" #658, then had to revise it's claim to "We currently do not expose a way to use WebContainer outside of StackBlitz.com,".
-
Lua: The Little Language That Could
> Wasm though seems like the likely general heir, and will have many different offerings for how to do that (Deno being one!).
I was recently blown away by some ideas that StackBlitz [0] apply based on WebContainers. The idea of a "server in the browser", they allow you to run Node-based environment like that via Wasm.
[0] https://stackblitz.com/
[1] https://webcontainers.io/
-
How repl.it and online code editors are built?
See https://webcontainers.io.
-
Blog Post: Reasonable Bootstrap
This very simple fact is well known flaw, which was already often criticized and asked for solutions by users. It doesn't only affect this kind of very exotic bootstrap applications but also significantly limits rusts usefulness in many other areas. Pure browser based scientific code documentation and example notebooks (e.g. jupyterLite) and sandboxed CI and IDE solutions (e.g. web containers) as available for many other languages are simply not available for rust because of this very fundamental issue.
-
WebContainer API
Looks like they plan to open it. From the FAQ section of README (https://github.com/stackblitz/webcontainer-core#faqs):
> Is there a developer API?
-
[AskJS] Is there an JavaScript engine agnostic server module that can be imported into Bun, QuickJS, Deno, and Node.js?
I'm skeptical about stackblitz claims. The last time I checked that is closed source code https://github.com/stackblitz/webcontainer-core/issues/658.
-
Use SSH in browser
StackBlitz claimed https://blog.stackblitz.com/posts/introducing-webcontainers/ to have implemented Node.js in the browser, though I have not observed any evidence of that being true and correct https://github.com/stackblitz/webcontainer-core/issues/658.
- Node.js in Chrome extension
-
Docker Desktop Requires A Paid Subscription, Now What?
The other honorable mention is StackBlitz, a web-based web editor for making containers that run Javascript applications. Interestingly, StackBlitz is championing WebContainers, a technology that allows developers to start NodeJS servers within the browser. The downside is, this technology only works with Javascript-based projects (NodeJS, NextJS, etc). I include it here because WebContainers could easily be extended to support other languages via WASM, like Ruby. I’ll also add in Buildah, a tool for building OCI images. I won’t say much about this tool because it’s designed for building images; you still need another service, like Podman, to actually create the containers.
What are some alternatives?
nodebox-runtime - Nodebox is a runtime for executing Node.js modules in the browser.
wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten
cwab - A simple, fast, and efficient background job processor for Rust
standards-positions
now - Node on Web
wasm-clang - Running Clang/LLD in WebAssembly Demo
wasmedge-quickjs - A high-performance, secure, extensible, and OCI-complaint JavaScript runtime for WasmEdge.
threads - Threads and Atomics in WebAssembly
native-messaging-deno - Deno Native Messaging Host
joystick - A full-stack JavaScript framework for building stable, easy-to-maintain apps and websites.
wasm-jseval - A safe eval library based on WebAssembly and Duktape/QuickJS.
openvscode-server - Run upstream VS Code on a remote machine with access through a modern web browser from any device, anywhere.