lagon
ComponentizeJS
lagon | ComponentizeJS | |
---|---|---|
7 | 2 | |
1,338 | 260 | |
0.0% | 3.1% | |
5.4 | 8.6 | |
8 months ago | 7 days ago | |
TypeScript | Rust | |
GNU Affero General Public License v3.0 | Apache License 2.0 |
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.
lagon
-
WinterJS
There’s also Lagon that solves that
https://github.com/lagonapp/lagon
-
Ask HN: What Are You Building?
I'm building Lagon, an open-source [1] runtime and platform that allows developers to run TypeScript and JavaScript serverless functions at the Edge, close to users. The runtime uses V8 Isolates and is written from scratch using Rust and rusty_v8 [2], Deno's Rust bindings for V8.
[1] https://github.com/lagonapp/lagon
[2] https://github.com/denoland/rusty_v8
-
Toolspace - A library of open-source developer tools, reviews, and alternatives. (Built on Next.js)
Looks really good. How can we submit new projects? I'd love to add Lagon, which is an open-source runtime and platform to deploy serverless functions: https://github.com/lagonapp/lagon
- Next.js 12.2: Middleware, On-Demand ISR, Experimental Edge SSR and API Routes
- How We Built Hydrogen: A React Framework for Building Custom Storefronts
-
I’m creating a Runtime for Serverless Functions, which will be deployed at the Edge. Anyone wants to help?
Of course it’s ok! Feel free to watch the repo (https://github.com/lagonapp/serverless) for news and updates
Here’s the repo: https://github.com/lagonapp/serverless
ComponentizeJS
-
The XOR Texture
If you were not worried about preventing external requests and were okay with it being able to make requests as an arbitrary webpage unrelated to your site could if opened, then loading the code in an iframe with the sandbox="allow-scripts" attribute is enough.
If you needed tighter sandboxing than that, then I think WebAssembly is your best bet because you can control exactly what APIs are exposed to a WebAssembly module. You could then let users submit WebAssembly modules or let them submit JS that will be run in a JS interpreter running in WebAssembly. I think https://github.com/justjake/quickjs-emscripten or https://github.com/fermyon/StarlingMonkey (used by https://github.com/bytecodealliance/ComponentizeJS) look like the best bets for that currently.
-
WinterJS
I don't think that's the intended use-case for this.
If you want to do this, I think something like ComponentizeJS[0] is what you would be looking for. As far as I can tell you'd also need to create WIT (Wasm Interface Type) definitions for the interface(s) that mod_wasm expects for its WASM modules, as they don't provide them themselves.
[0]: https://github.com/bytecodealliance/componentize-js
What are some alternatives?
workerd - The JavaScript / Wasm runtime that powers Cloudflare Workers
weval
scale - A framework for building high-performance plugin systems into any application, powered by WebAssembly.
esbuild - An extremely fast bundler for the web
radash - Functional utility library - modern, simple, typed, powerful
quickjs - Public repository of the QuickJS Javascript Engine.
storage - Vercel Postgres, KV, Blob, and Edge Config
hydrogen-vercel-edge - Deploy a Hydrogen storefront to Vercel Edge Functions
rusty_v8 - Rust bindings for the V8 JavaScript engine
solid-site - Code that powers the SolidJS.com platform.