Hacker News Reader

I don't think I understand your last point. Could you elaborate? What does "Javascript/Typescript support" mean to you (i.e. what specific features/capabilities are missing from the current engines)?

View on HN

I mean compiling JS/TS to WASM or running a JS runtime like bun inside WASM

JS/TS interop, sure--but what are the use cases for running a JS runtime inside WASM?

Iirc, Shopify uses this to execute storefront code on the edge in a sandboxed environment.

People who want to write JavaScript for backend store functionality can, and then Shopify deploys that code into containers with small IO semantics

I believe Shopify looked into using a JS engine in WASM for front end sandboxing but ended up using a wrapper around the Shadow Realms API instead.

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.

Reply on news.ycombinator.com