-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no member named
errors with node-addon-api@^5
#1029
Comments
no member named
error with node-addon-api@^5no member named
errors with node-addon-api@^5
node : v20.10.0 for this version we are able to install both dependency in windows without getting any failure. |
My original reproduction was with pnpm latest (also tried the v9 beta), I've added this detail and the version number above. |
WorkaroundUse npm Overrides, Yarn Resolutions or pnpm Overrides to force upgrade the version of {
"pnpm": {
"overrides": {
"node-addon-api": "8.1.0"
}
}
} From our first tests, this There's an open PR to upgrade here too: |
in case you are not using pnpm, you can simply do that:
|
What went wrong?
Installing
sharp@0.33.2
andbcrypt@5.1.1
together causesno member named
errors:Error logs:
Upon further investigation, there is an older version of
node-addon-api
(version5.1.0
) in the pnpm lockfile, which appears to be causing the issue (sharp
requiresnode-addon-api@>=7.0.0
):Also visible in the
bcrypt
package.json
:node.bcrypt.js/package.json
Line 33 in d8195c6
Removing the
bcrypt
from thepackage.json
appears to make the error go away again.What did you expect to happen?
bcrypt@5.1.1
should be able to coexist withsharp@0.33.2
without causingsharp
build failuresWhich version of nodejs and OS?
Node.js: v20.12.1
Package manager: pnpm (latest and v9 beta)
macOS: Sonoma 14.4.1 (23E224)
The text was updated successfully, but these errors were encountered: