Vendor more recent node version?

Open
#1,064 9 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
node.js

Research direction

Start by tracing emsdk's configuration for the vendored Node.js version and the platform-specific packages that provide it. Confirm where v14.18 is selected, then verify that the requested newer LTS version is bundled consistently and that the documented WebAssembly BigInt behavior no longer depends on the old Node flag.

Written by the indexing model from the issue text.

Description

Emsdk includes node v14.18 which is quite old. In particular, one annoying thing about it is that it requires the --experimental-wasm-bigint flag which is poorly documented (it doesn't appear in node --help) and future versions of node error out if passed --experimental-wasm-bigint so it's pretty hard to handle new and old nodes. Also, the error message wasm function signature contains illegal type has nothing that suggests it has anything to do with -sWASM_BIGINT or with --experimental-wasm-bigint or anything. This is wasting a fair amount of time for various people who are seeing this bug and having to investigate. I think it would help a lot to vendor a newer version, say v16.15 LTS.

Dominant language
Python
Stars
3.7k
Forks
822
Avg merge
2d 6h
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from emscripten-core/emsdk

All issues in emscripten-core/emsdk

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.