-
Notifications
You must be signed in to change notification settings - Fork 1.2k
npm install fails with missing git hook #1444
Comments
This is due to a broken symlink in the |
Looking into this it looks like Aegir < 15 was using the Aside from doing a pre-install removal in aegir, which is probably unnecessary for this, the removal is the quickest fix. |
Is this OSX specific? It never happened to me (I'm on Linux). |
Possibly, I am also on OSX. I can try replicating later today on Linux. |
Although I prefer having pre-push hooks, I also don't want to see everyone's project broken. I wonder if there's a workaround/better solution. |
Okay, I was able to replicate this consistently with docker, however, it only occurs if the node_modules are removed in between npm installs. Anyone who didn't manually remove the node_modules prior to the install probably won't have the issue. I don't think we need to do any code changes for this. In theory we could create some backward compatibility support via preinstall scripts, but since we're still in beta releases I think it's okay to just add a quick note about upgrading to 0.30 to the readme in case anyone hits the issue. Here are the Dockerfile contents for reference: Works
Fails
|
This makes sense. Unfortunately, chances are very high that users do this. Will send a PR to have note int he README. |
Closes ipfs#1444 License: MIT Signed-off-by: Pascal Precht <pascal.precht@gmail.com>
Closes ipfs#1444 License: MIT Signed-off-by: Pascal Precht <pascal.precht@gmail.com>
Closes ipfs#1444 License: MIT Signed-off-by: Pascal Precht <pascal.precht@gmail.com>
Turns out that, similar to ipfs/js-ipfs#1444, we've introduce a regression in ipfs-inactive@87a8f96 in which we upgrade Aegir to 15.0.0. This causes problems during installation of npm dependencies for any existing clone of the repository as the pre-push hook becomes a dead symlink. License: MIT Signed-off-by: Pascal Precht <pascal.precht@gmail.com>
Turns out this is happening over at |
The proper solution is to make git-validate not fail. Let's hope this PR gets accepted: nlf/git-validate#67 |
Closes ipfs#1444 License: MIT Signed-off-by: Pascal Precht <pascal.precht@gmail.com>
Nice @vmx ! |
Closes #1444 License: MIT Signed-off-by: Pascal Precht <pascal.precht@gmail.com>
With the change from `pre-push` to `git-validate` there was an issue when you were removing `node_modules` before upgrading to AEgir 15.0.0. (see ipfs/js-ipfs#1444 for more). On the most recent version of git-validate that issue was fixed.
With the change from `pre-push` to `git-validate` there was an issue when you were removing `node_modules` before upgrading to AEgir 15.0.0. (see ipfs/js-ipfs#1444 for more). On the most recent version of git-validate that issue was fixed.
With the change from `pre-push` to `git-validate` there was an issue when you were removing `node_modules` before upgrading to AEgir 15.0.0. (see ipfs/js-ipfs#1444 for more). On the most recent version of git-validate that issue was fixed.
v9.11.1
and npmv6.1.0
)Type: Bug
Severity: High
Description:
npm install
fails with:Steps to reproduce the error:
npm i
The text was updated successfully, but these errors were encountered: