javy

It's not front end sandboxing. It's edge function sandboxing. And they do indeed have this in prod: https://shopify.dev/docs/apps/build/functions/programming-la... > Shopify CLI compiles your JavaScript code using Javy, our JavaScript-to-WebAssembly toolchain. I've actually used Javy. Kind of interesting: https://github.com/bytecodealliance/javy.

Convenience helper for that: https://github.com/bytecodealliance/javy

I recommend trying Javy[0]. Javy allows you to build a WASM file that includes Javy's JS interpreter along with your JS source code. Note that Javy is a heavily sandboxed environment so it doesn't have access to the internet, or npm modules, a desirable feature for running user code. We're building an IoT Cloud Platform, Fostrom[1] where we're using Javy to power our Actions infrastructure. But instead of compiling each Action's JS code to a Javy WASM module, I figured out a simpler way by creating a single WASM module with our wrapper code (which contains some further isolation and helpful functions), and we provide the user code as an input while executing the single pre-compiled WASM module. [0] https://github.com/bytecodealliance/javy [1] https://fostrom.io

As someone who uses bun,deno & cloudflare workers, I want to say that atleast in bun, the wasm part actually happens itself in js and bun just runs that js using javascriptcore which is definitely not optimized as it is stated by Bun docs themselves (https://bun.sh/docs/runtime/loaders#wasi) Also I am still not sure how you are thinking that this project is similar to Bun. Bun is for javascript, somebody runs wasm in js and that on bun... Faasta runs wasm directly and you would need to use javy to actually run js in Faasta https://github.com/bytecodealliance/javy Its sort of like a->b or b->a and faasta is way more leaner and better... Though bun is good if you are all Typescript. Still I am sure I am not able to explain myself clearly, so do ask me something if you think I haven't explained quite properly and I am obviously sorry about t

I have an instrumented version of QuickJS that can be used in the javy toolchain: https://github.com/bytecodealliance/javy There are two primary goals: 1. Emit metrics directly about the QuickJS runtime similar to node metrics 2. Expose the Observe API as js bindings With the Observe API exposed to JS, you can do manual instrumentation. I have also instrumented the pieces of QuickJS that invoke JS functions in order to automatically emit spans and it works, but still trying to fill some information gaps to make it more usable than manual instrumentation. > are you wiring it up like how APM is wired up in JVM applications or what exactly are you doing? Does it effect stack trace outputs or leave those alone? I can't speak to how JVM does it, but no this does not effect the call stack.

Related links from the article: Javy: JS to WebAssembly toolchain - https://github.com/bytecodealliance/javy Bringing Javascript to WebAssembly for Shopify Functions - https://shopify.engineering/javascript-in-webassembly-for-sh...

Late to the party, but I didn't see anyone mentioning this: Shopify seems to be curiously extremely involved in sponsoring WebAssembly-related projects. It's a gold sponsor on AssemblyScript[1], it used to develop javy[2] which compiles JavaScript to WebAssembly, a member of the BytecodeAlliance[3]. I wouldn't think they sponsor LadyBird just for LibWasm[4], as that doesn't make any sense, but technically, they add that to their wasm sponsorships now. Honestly, it looks like a really nice place to work if you like WebAssembly, I wouldn't mind a collaboration or to work with them. [1] https://www.assemblyscript.org/ [2] https://github.com/Shopify/javy [3] https://bytecodealliance.org/ [4] https://github.com/SerenityOS/serenity/tree/master/Userland/...

This post demonstrates how to implement plugins for Rust using QuickJS in WebAssembly for safe arbitrary code execution. It relies heavily on on the work done by Shopify with Javy (https://github.com/Shopify/javy) but makes the deployment process easier. I hope it is useful.

This post demonstrates how to implement plugins for Rust using QuickJS in WebAssembly for safe arbitrary code execution. It relies heavily on on the work done by Shopify with Javy (https://github.com/Shopify/javy) but makes the deployment process easier. I hope it is useful.

I’m not sure if anyone has done so yet for Go, but Shopify has done this for Rust. https://github.com/Shopify/javy/tree/main/crates/quickjs-was...

> - JS is notably missing from the list of languages supported on the front page. But I see mentions of a Spidermonkey.wasm in the blog post. Is running JS on top of wasmtime in production a realistic prospect today? If so, where can I read more? (mainly interested in this for the instantiation time benefits, though maybe all/most of that will be negated by the embedded JS engine?) Shopify and others use QuickJS as their JS engine of choice. See https://github.com/Shopify/javy as a starting point. The real benefit is allowing authors of plugins to write JS and not AssemblyScript, not any performance or instantiation time benefits. > - How should I go about building a typical web service on top of wasmtime? Can wasmtime itself handle network requests/connections or would I need to build the web server in some other host language and pass r