This release is a pre-release and may not be stable for production use.
Unoffical Node.js wheels
nodejs-wheel is an unofficial repository to distribute Node.js prebuilt wheels through PyPI using
pip install nodejs-wheel
New in v20.13.0: If you don't need command line interface (CLI), install only nodejs-wheel-binaries, which is a direct dependency of nodejs-wheel.
pip install nodejs-wheel-binaries
The package requires Python 3.7 and above.
The project is powered by scikit-build-core and cibuildwheel.
Available Builds
| OS | Arch | Bit | Conditions | New in |
|---|---|---|---|---|
| Linux | x86_64 | 64 | glibc >= 2.17 | v18.18.0 |
| Linux | x86_64 | 64 | musl >= 1.2 | v20.14.0 |
| Linux | aarch64 | 64 | glibc >= 2.17 | v20.13.0 |
| macOS | x86_64 | 64 | >= macOS-11 | v18.18.0 |
| macOS | arm64 | 64 | >= macOS-11 | v20.11.1 |
| Windows | amd64 | 64 | v18.18.0 | |
| Windows | arm64 | 64 | v22.12.0 |
Usage
Command line
Only available in the nodejs-wheel package.
node -h
npm -h
npx -h
Run library module as a script
New in v20.13.0.
Only support node.
python -m nodejs_wheel --version
Python API
New in v20.13.0.
from nodejs_wheel import (
node,
npm,
npx,
)
return_code0 = node(["--version"])
return_code1 = npm(["--version"])
return_code2 = npx(["--version"])
New in v20.13.1: pass return_completed_process=True to get subprocess.CompletedProcess instead of int.
completed_process0 = node(["--version"], return_completed_process=True)
completed_process1 = npm(["--version"], return_completed_process=True)
completed_process2 = npx(["--version"], return_completed_process=True)
License
nodejs-wheel distributed under the same MIT license as Node.js.
Other projects
The project is inspired by many other similiar projects:
- samwillis/nodejs-pypi: The package redistribute the official Node.js binaraies to PyPI. However, the offical binary for Nodejs 18 requires GLIBC 2.28, making it unsupported in manylinux2014 images. Besides, the wheel tag is wrong.
- sbwml/node-latest-centos: Use GitHub Actions to build Node.js in CentOS 7, but is not related to Python or PyPI.
- scikit-build/cmake-python-distributions: Use cibuildwheel and scikit-build to build CMake and distribute CMake in PyPI.
1 maintainer
Metadata
1 maintainer
Release files for nodejs-wheel 23.6.0rc0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| nodejs_wheel-23.6.0rc0.tar.gz | 2.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nodejs_wheel-23.6.0rc0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.9 kB
Release files / nodejs_wheel-23.6.0rc0.tar.gz
| Download URL | nodejs_wheel-23.6.0rc0.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f6ac1653f5bb8e1a67c4ea82720ee5c1d6b84f395d6689556bda53920e2b5c7a
|
|
BLAKE2b-256 checksum How to use checksums |
e97d84870d9bf7816fcba2ac253b954b9c776120d4528c799a8b2499b5c7aa79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 9, 2025.
Transparency logRelease files / nodejs_wheel-23.6.0rc0-py3-none-any.whl
| Download URL | nodejs_wheel-23.6.0rc0-py3-none-any.whl |
|---|---|
| Size | 4.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fdfad120afe4467723c37c5d23f26b4baf68c26d2c411bbc1e213895f3d6534d
|
|
BLAKE2b-256 checksum How to use checksums |
9af65c37412c4db8e072e2ea25087d145b27d1ef979643e52da1b5e638571a5a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 9, 2025.
Transparency log
