emscripten-core/emscripten

Publish emsdk on npm + integrate with npm

Open

#5,774 opened on Nov 13, 2017

View on GitHub
 (28 comments) (14 reactions) (0 assignees)C++ (27,361 stars) (3,519 forks)batch import
help wantedwontfix

Description

Right now it's kind of kludgy to create npm packages that are built from C sources using Emscripten. Normally, when doing a local 'npm install', the devDependencies for the package are pulled from npm. But if Emscripten is a development dependency, people need to "manually" install emsdk, activate the right version, etc. It would be great if Emscripten could also be pulled from npm to 1) make this less kludgy 2) enable automatically activating the Emscripten/node/llvm versions required for the project in question, for example based on additional info in the package.json file.

Contributor guide

Tech stack
ccppwasmjavascriptnodejsshell
Domain
toolingdeveloper experiencebuild systemcli
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
npm package managementEmscripten SDK structureshell scripting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
First, explore the existing emsdk repository (https://github.com/emscripten core/emsdk) to understand its structure and how it manages different versions of Emscripten, Node, and LLVM. Review the npm documentation for creating packages and consider how to publish emsdk as an npm package that handles version management automatically. Look at the issue comments for any suggested approaches or maintainer requirements. Reach out to maintainers for clarity on desired implementation details before proceeding.