I don't think there is one, but we could allow a relaxed minimum bound and an upper bound on an unreleased version of Node.js, so that we can enable users to flexibly install another version if they want to. There are no other Pythonic dependencies, so we won't have any troubles with conflicts.

This means that we can specify the dependency as:

dependencies = [
  "...",
  "nodejs-wheel>=20,<25",
  "...",
]

or a similar variation, such that the lower bound is the minimum version of Node.js that Pyodide supports (I marked 20 but maybe it still works on 18), and the upper bound is one version higher than an incoming Node.js LTS version, which is always an even number (24, in this case).

This would prevent us from installing Node.js 25 or 26. Though, this doesn't address if something breaks with Node.js 24, though, so maybe we can leave it at <=22 and consider relaxing the requirement only if someone requests for it.

Another way I'm thinking of is to bundle https://github.com/nvm-sh/nvm for PyPI. I've wrapped non-Python binaries into wheels before; see https://github.com/agriyakhetarpal/hugo-python-distributions/.

Should we bundle our own copy of Node.js to work with pyodide venv? #119

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Should we bundle our own copy of Node.js to work with `pyodide venv`? #119