Failed at the git-validate@2.2.2 install script 'node bin/install'

[brityboy]

During npm install, I received the errors below. I attached the npm-debug.log file as well by generating it with npm run test. Hope this information is helpful. Thanks!

sh: 1: node: not found
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.17
npm ERR! Linux 4.4.0-62-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v4.2.6
npm ERR! npm  v3.5.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn

npm ERR! git-validate@2.2.2 install: `node bin/install`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the git-validate@2.2.2 install script 'node bin/install'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the git-validate package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node bin/install

npm-debug-log.txt

[mikewli]

Seems like there might be a problem with your existing git hooks, where the install script tried to install over the existing hooks, but it doesn't have permission (most likely).

You should be able to delete/rename those hooks by going into your .git/hooks, and it should work after that when you try to re-install.

[kimett]

Got similair results so renamed .git/hooks to take that out of the equation and also tried in a freshly npm init
Both tries still failing so wondering if it maybe is something else than hooks?

$ npm install git-validate


> git-validate@2.2.2 install /home/kimi/vizceral-example/node_modules/git-validate
> node bin/install

sh: 1: node: not found
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.1.1
npm ERR! Linux 4.4.0-47-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "git-validate"
npm ERR! node v4.2.6
npm ERR! npm  v3.5.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn

npm ERR! git-validate@2.2.2 install: `node bin/install`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the git-validate@2.2.2 install script 'node bin/install'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the git-validate package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node bin/install
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs git-validate
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls git-validate
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/kimi/vizceral-example/npm-debug.log

147 info lifecycle git-validate@2.2.2~install: git-validate@2.2.2
148 verbose lifecycle git-validate@2.2.2~install: unsafe-perm in lifecycle true
149 verbose lifecycle git-validate@2.2.2~install: PATH: /usr/share/npm/bin/node-gyp-bin:/home/kimi/vizceral-example/node_modules/git-validate/node_modules/.bin:/home/kimi/vizceral-example/node_modules/.bin:/home/kimi/bin:/home/kimi/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
150 verbose lifecycle git-validate@2.2.2~install: CWD: /home/kimi/vizceral-example/node_modules/git-validate
151 silly lifecycle git-validate@2.2.2~install: Args: [ '-c', 'node bin/install' ]
152 info lifecycle git-validate@2.2.2~install: Failed to exec install script
153 verbose unlock done using /home/kimi/.npm/_locks/staging-2c9ab73f2d53a43f.lock for /home/kimi/vizceral-example/node_modules/.staging
154 silly rollbackFailedOptional Starting
155 silly rollbackFailedOptional Finishing
156 silly runTopLevelLifecycles Starting
157 silly runTopLevelLifecycles Finishing
158 silly install printInstalled
159 warn optional Skipping failed optional dependency /chokidar/fsevents:
160 warn notsup Not compatible with your operating system or architecture: fsevents@1.1.1
161 verbose stack Error: git-validate@2.2.2 install: `node bin/install`
161 verbose stack spawn ENOENT
161 verbose stack     at ChildProcess.<anonymous> (/usr/share/npm/lib/utils/spawn.js:17:16)
161 verbose stack     at emitTwo (events.js:87:13)
161 verbose stack     at ChildProcess.emit (events.js:172:7)
161 verbose stack     at maybeClose (internal/child_process.js:821:16)
161 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
162 verbose pkgid git-validate@2.2.2
163 verbose cwd /home/kimi/vizceral-example
164 error Linux 4.4.0-47-generic
165 error argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "git-validate"
166 error node v4.2.6
167 error npm  v3.5.2
168 error file sh
169 error code ELIFECYCLE
170 error errno ENOENT
171 error syscall spawn
172 error git-validate@2.2.2 install: `node bin/install`
172 error spawn ENOENT
173 error Failed at the git-validate@2.2.2 install script 'node bin/install'.
173 error Make sure you have the latest version of node.js and npm installed.
173 error If you do, this is most likely a problem with the git-validate package,
173 error not with npm itself.
173 error Tell the author that this fails on your system:
173 error     node bin/install
173 error You can get information on how to open an issue for this project with:
173 error     npm bugs git-validate
173 error Or if that isn't available, you can get their info via:
173 error     npm owner ls git-validate
173 error There is likely additional logging output above.
174 verbose exit [ 1, true ]

$ ls -a .git/
.   branches  description  hooks_org  info  objects      refs

[nlf]

ahh, your node binary is named "nodejs" not "node", i'll see if i can figure out a fix. a temporary workaround would be to make a symlink

[kimett]

Default Ubuntu install from what I remember.

Symlink fixes that problem, on that machine at least.