@mapbox/node-pre-gyp is a Node.js tool that helps publish and install Node.js C++ addons from pre-built binaries instead of compiling from source. It provides a command line workflow (install, package, publish, unpublish, info, and more) and a JavaScript API to locate the installed binary.
Project status
- Active maintenance: The GitHub repository shows a recent upstream push on 2026-08-11, indicating ongoing work, but the latest provided tagged updates are from 2025-12-19 (v2.0.4-pre.0).
- Update cadence: Most recent tagged updates cluster in Nov to Dec 2025 (v2.0.1 in May 2025, v2.0.2 to v2.0.3 in Nov 2025, and v2.0.4-pre.0 in Dec 2025). Since then, there is a tag gap of ~8 months up to today (2026-08-13), even though there are newer commits.
AI summary generated
Recent updates
v2.0.4-pre.0
Release v2.0.4-pre.0 is a pre-release intended to test the release workflow. The diff shows only metadata updates (version and changelog entry), with no application logic changes.
v2.0.3
Release v2.0.3 is primarily a dependency revert, undoing a previous attempt to bump the internal dependency nopt. The diff also updates CI workflows to use a newer GitHub Actions checkout action.
v2.0.2
v2.0.2 extends node-pre-gyp to support publishing binaries to S3 with configurable ACLs, instead of always using a public-read ACL. The implementation also changes install behavior to handle private S3 binaries by attempting an authenticated download when the initial HTTP fetch is forbidden. CI workflow actions and several dependency versions were updated as part of this release.
Featuresv2.0.1
v2.0.1 primarily updates the ABI crosswalk to cover Node ABI 137 for Node 24. In addition to the crosswalk change, this release substantially refactors S3 mocking behavior (used for tests and local installs) and adds a new S3 test workflow plus related test fixtures.
BreakingFeaturesv2.0.0
Release v2.0.0 is described as a finalization of the 2.0.0-rc.0 release, including Node support policy updates and several dependency-related adjustments. However, the provided code diff only shows version metadata updates (changelog and package.json/package-lock.json), with no functional or behavioral code changes visible in the diff.
Breakingv2.0.0-rc.0
This release primarily updates runtime and dependency support. It now targets stable Node.js releases 18 and above, and includes dependency upgrades plus a packaging-related fix for S3 force path style during installation.
Breaking