Run JavaScript anywhere. Safely.

---

Edge.js is a secure JavaScript runtime, designed for Edge computing and AI workloads.

Edge.js uses WebAssembly for sandboxing when in --safe mode, so even the most insecure programs can run on it safely. Edge also is:

• ✅ Fully compatible with Node.js.
• 🔒 Sandboxed by design.
• 🧩 Pluggable with any JS engine: V8, JavaScriptCore or QuickJS.
• 💪 Compatible with any package manager: NPM/PNPM/Yarn/Bun.

Install Edge.js

curl -fsSL https://edgejs.org/install | bash

Use it!

You can use it as you would do it with Node.js:

const http = require("node:http");

http
  .createServer((_req, res) => {
    res.end("hello from edge\n");
  })
  .listen(3000, () => {
    console.log("listening on http://localhost:3000");
  });

$ edge server.js

If you want to use it in your current workflow, just wrap your commands with edge:

$ edge node myfile.js
$ edge npm install
$ edge pnpm run dev

Development

First, clone the repo and initialize only the napi submodule:

git clone --recurse-submodules https://github.com/wasmerio/edgejs.git
cd edgejs

Build the CLI locally:

make build
./build-edge/edge server.js

./build-edge/edge --run dev

Or run the tests:

make test
NODE_TEST_RUNNER="$(pwd)/build-edge/edge" \
./test/nodejs_test_harness --category=node:assert

Host-JavaScript WASIX package

The root wasmer.toml describes the engine-free syrusakbary/edgejs package. Its WebAssembly module imports the standard N-API surface from napi and the EdgeJS extension surface from napi_extension_wasmer_v0; it does not embed QuickJS or V8. A compatible host provides those imports using its own JavaScript engine.

make build-wasix
make validate-wasix-imports
wasmer package build --check .

The build runs the import/engine validation automatically. The embedded QuickJS package remains separately available under quickjs-wasm/.

WASIX static data

WASIX builds do not embed the builtin JavaScript sources or the ICU data in the wasm module. Wasm has no read-only data segment, so embedded data was copied into every instance's linear memory (about 45 MB). Reading it from the package filesystem cuts each instance's linear memory from 51.6 MB to about 11 MB (wasmer-sdk#547). Native builds still embed both.

After linking, both WASIX build scripts stage the data next to the wasm:

• build-wasix/node-lib/ (or build-quickjs-wasix/node-lib/): the builtin JS files, with deps JS under internal/deps/ and a .edge-builtin-catalog digest file. The guest reads it from /node-lib.
• build-wasix/icu/ (or build-quickjs-wasix/icu/): ICU 78 as individual item files under icudt78l/. The guest reads it from /usr/share/edge-icu.

Both package manifests map these directories, so wasmer run . and wasmer run quickjs-wasm need no extra flags. To run the raw host N-API wasm with napi_wasmer (make build-napi-wasmer-cli), pass the staged trees yourself:

build-wasix-napi/target/release/napi_wasmer build-wasix/edgejs.wasm \
  --builtin-js-dir build-wasix/node-lib \
  --mount "$PWD/build-wasix/icu:/usr/share/edge-icu" \
  -- -e "console.log(new Intl.DateTimeFormat('de', {month: 'long', timeZone: 'UTC'}).format(0))"

The guest checks the lib root and its catalog digest before bootstrap. A missing or mismatched /node-lib is a hard error. Overrides:

• EDGEJS_LIB_DIR: a different guest lib root (deps under $EDGEJS_LIB_DIR/internal/deps). A digest mismatch there is only a warning.
• --icu-data-dir, then EDGE_ICU_DATA, then NODE_ICU_DATA, then ICU_DATA: a different guest ICU data directory, holding either icudt78l/ or icudt78l.dat. A setting that holds neither prints a warning and falls back to /usr/share/edge-icu.

Set EDGE_WASIX_EMBED_STATIC_DATA=1 when building to keep both embedded. This gives a standalone wasm that needs no data mounts but keeps the larger per-instance memory. It builds into its own directory (build-wasix-embedded/ or build-quickjs-wasix-embedded/), which the package manifests do not use.

Both WASIX packages expose npm as an alias for the bundled pnpm CLI. They retain real npm as edge-npm-internal and configure pnpm's npm-path to use it for delegated operations, avoiding recursive calls to the alias.

This host-engine mode is experimental. The buffer ownership and synchronization contract is documented in 004_buffer_ownership.md, and deferred security work is recorded in SECURITY-HOST-JS-NAPI.md. The browser regression gate covers package installation, timers, promises, workers, networking, HTTP, and a rendered Next.js development preview.

Contribute 🤗

We have created a public ROADMAP, so you can contribute into the project easily!

• 0.x Production readiness: platform coverage across Linux, Windows, macOS, iOS, and Android; reliability in constrained environments; security audits; and successful real production use.
• 1.x Need for speed: faster startup, faster core paths, and performance that competes with or beats Node.js, Bun, and Deno on most workloads.
• 2.x Enhancements: first-class TypeScript support and a smoother developer experience.

For architecture detail, see ARCHITECTURE.md.