bytecodealliance / bytecodealliance/ComponentizeJS

Dynamic Linking of SpiderMonkey Interpreter

Open
#66 3 comments 3 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
391
Forks
53
Avg merge
3d 5h
Merged PRs (30d)
1

Description

**Problem**

The size of wasm module produced is quite high, ~ 8 MB for a function adding two numbers. My understanding is that the interpreter (SpiderMonkey) is the majority of it.

**Query**

Is there a way to dynamically link the interpreter and wasm module to reduce the module size? The primary benefit is when there are multiple wasm modules & instances

For reference: [Javy](https://shopify.engineering/javascript-in-webassembly-for-shopify-functions) has -d flag for enabling dynamic linking

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no repository files, tests, or entry points. Start by tracing how ComponentizeJS packages the SpiderMonkey interpreter and wasm modules, using the linked Javy -d reference for comparison; done requires a documented or implemented dynamic-linking approach that reduces repeated interpreter size across modules.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, rust, wasm
Domain
build-system
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.