Bump userid from 1.0.0-beta.9 to 1.2.5 #558
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This solves a build failure on Debian Bookworm. We face the same error on all architectures: x86, ARM, 32-bit, 64-bit, RISC-V. Interestingly on Debian Bullseye and Trixie, it does not happen. Node versions are all the same latest v23.1.0 on all platforms, the Python 3 version is different, and the C++ compiler and library versions, where it seems so face a syntax error in
node-addon-api/napi.h
.As it happenes during
userid
build, I recognised that the dependency is declared with a beta version. Checking available versions, it turns out stat1.0.0-beta.9
was for whatever reason uploaded 4 seconds after stable1.0.0
and hence seems unintentionally taken as latest^1.0.0
bynpm
. However, there is a newer1.2.5
release, and it seems to work fine with MineOS, solving the build issue in the same turn.https://www.npmjs.com/package/userid?activeTab=versions
Log