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
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
❯ npm i [email protected]
npm WARN lifecycle The node binary used for scripts is /Users/adam/.asdf/shims/node but npm is using /Users/adam/.asdf/installs/nodejs/8.9.4/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
> [email protected] install /private/tmp/dummy/node_modules/keyboard-layout
> node-gyp rebuild
nodejs 0.11.13 not installed
npm WARN [email protected] No description
npm WARN [email protected] No repository field.
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] install: `node-gyp rebuild`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/adam/.npm/_logs/2018-06-14T00_13_51_842Z-debug.log
❯ npm doctor
Check Value Recommendation
npm ping OK
npm -v v5.6.0 Use npm v6.1.0
node -v v8.9.4 Use node v8.11.3
npm config get registry https://registry.npmjs.org/
which git /usr/local/bin/git
Perms check on cached files ok
Perms check on global node_modules ok
Perms check on local node_modules ok
Verify cache contents verified 2008 tarballs
Click to expand 2018-06-14T00_13_51_842Z-debug.log
I installed node 0.11.13 and didn't set it as my active node version, and somehow that fixed this. I don't know what is looking for such an old node version or how it even found it, since I have v8.15.0 active, but that seems to fix it. 🤷♂️
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Click to expand 2018-06-14T00_13_51_842Z-debug.log
The text was updated successfully, but these errors were encountered: