You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can see the full error logs here. Long story short installing via npm i git+https://github.com/nodegit/nodegit.git#4561dcb7c120474a4553baa27e4c4c2f4be23a2b is broken because for whatever reason the binding.gyp file is not being correctly generated in the build process.
which is odd since fs-extra is in package.json as expected. I wonder: does npm distinguish between build-time dependencies and runtime dependencies? Perhaps that would explain this failure.
Activity
ianhattendorf commentedon Oct 15, 2021
If you have some time to investigate:
This is probably due to
isGitReponodegit/utils/buildFlags.js
Line 10 in 4da92c9
false, causinggenerateto not be callednodegit/lifecycleScripts/preinstall.js
Line 33 in 4da92c9
The build system is pretty old, so it's possible this option just wasn't considered.
samuela commentedon Oct 16, 2021
Thanks @ianhattendorf! I can poke around a little bit, but I don't have much experience with npm/gyp.
One thing that I have noticed is that I get a different error altogether when attempting to install globally:
Full logs here. Looks like some kind of issue running node-pre-gyp...
samuela commentedon Oct 17, 2021
Looking at this a bit more: Why not just remove the isGitRepo check here:
nodegit/lifecycleScripts/preinstall.js
Lines 28 to 35 in 4da92c9
Is there a reason to not run
submodulesandgeneratein some cases?Fix nodegit#1864
samuela commentedon Oct 17, 2021
Ok, I tried fixing in samuela@b74a591. Now seeing a new error (full log here):
which is odd since
fs-extrais in package.json as expected. I wonder: does npm distinguish between build-time dependencies and runtime dependencies? Perhaps that would explain this failure.ianhattendorf commentedon Oct 20, 2021
I believe this is for supporting non-git installs (e.g. tarballs), but that appears to be broken (
npm icomplains about missingdist/nodegit.js)Some scripts run during the
preinstallstep, where packages aren't yet installed (e.g.nodegit/utils/execPromise.js
Line 3 in 031fd00
marvindanig commentedon Oct 23, 2021
In my case, the installation fails with the
node:16-stretchimage because it does not find python. The full error output is over here.This is weird because I specifically install python right before the
npm cistep on my dockerfile:marvindanig commentedon Oct 23, 2021
I got a new error the second time which I tried with the newest version of
nodegitandnode:17-stretchimage.samuela commentedon Oct 23, 2021
Looks like it's not finding the correct version of OpenSSL headers it's looking for...
marvindanig commentedon Oct 25, 2021
OTOH the build succeeded for my web-app without issues with the
node:15-stretchimage.Vadorequest commentedon Jul 17, 2022
I also tried to use that "pattern" to try to authenticate using oauth through the url, but it failed, too.