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
node-gyp rebuild is triggered when using a private registry #2988
Comments
|
Yes but who is trying to load |
node-gyp/gyp/pylib/gyp/input.py Line 2991 in 391cc5b
|
HI @cclauss , |
Perhaps |
Hi @cclauss, |
Do any ideas from #2714 help? |
We started seeing the same behavior yesterday. The package I tried to install is different ( I'm using nvm locally on macos but we saw that on our CI build (using linux) as well. If I remove our custom registry from Running
However when I try to install from npmjs I see:
I don't know very well the in-and-outs of npm and node-gyp to understand why this would be different and if that's relevant, or if even if we need to configure something on our registry... |
These repos are launching |
@cclauss I'm digging into this and to me, some node-gyp-build script doesn't behave the same when using a private registry. |
The package I mentioned is just one example, actually any package that needs native build had this issue for us. |
Hi, maintainer of pact-js-core here. the binding.gyp is purposely excluded from the published npm package, as prebuilt node bindings for all platforms are shipped in the npm module. node-gyp is a dependency in the project, in order to load the bindings at runtime. We do not expect, or want node-gyp to trigger at install time, regardless of the users I would imagine lifting the required code from node-gyp, and removing the dependency with solve this issue for end users that suffer it. I was not able to reproduce with a locally running verdaccio instance Full slack thread from the OP regarding this issue is here in our slack archive |
v18.19.1 and npm 10.2.4
Darwin Kernel Version 23.2.0: Wed Nov 15 21:54:05 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6031 arm64
Apple clang version 15.0.0 (clang-1500.1.0.2.5)
Target: arm64-apple-darwin23.2.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bi
Verbose output (from npm or node-gyp):
When trying to install
@pact-foundation/pact-core
only using a private registry, I get the error above. If I try to install the same package from npmjs.com it works.I tried to download the package from our private registry with the browser and install it manually in the project and it also works.
In the logs, the main difference between using the private registry or npmjs.com, is that when using the private registry, the command
node-gyp rebuild
is executed but it should not be.Any idea?
The text was updated successfully, but these errors were encountered: