-
Notifications
You must be signed in to change notification settings - Fork 54
Error activating node version #37
Comments
Please be sure to include the appropriate debugging output. Can you also provide the following:
|
$ nvm --version
0.29.0
$ __avn_debug
avn could not activate node 5.1
error: no plugin passed predicate
avn-nvm: nvm exited with status: 127
/bin/bash: /Users/m089269/.nvm/nvm.sh: No such file or directory
/bin/bash: nvm: command not found
$ ls -al ~/.nvm
total 0
drwxr-xr-x 5 m089269 MFAD\Domain Users 170 Nov 25 11:14 .
drwxr-xr-x+ 74 m089269 MFAD\Domain Users 2516 Jan 19 15:55 ..
drwxr-xr-x 3 m089269 MFAD\Domain Users 102 Nov 25 11:15 alias
drwxr-xr-x 3 m089269 MFAD\Domain Users 102 Nov 25 11:14 bin
drwxr-xr-x 3 m089269 MFAD\Domain Users 102 Nov 25 11:14 versions I'm on OSX El Capitan running the default terminal app (let me know if there's a better way to get the shell version) |
Any update on this? |
@toymachiner62 it appears as though you installed via homebrew which is not supported. See: If that's not the case, then your |
I just reinstalled nvm via their install curl command and I'm still getting the error: $ cd myapp/
avn could not activate node 5.1 $ __avn_debug
avn could not activate node 5.1
error: no plugin passed predicate
avn-nvm: nvm exited with status: 127
/bin/bash: /Users/myuser/.nvm/nvm.sh: No such file or directory
/bin/bash: nvm: command not found
|
The absense of the @ljharb can you confirm? My suggestion (and please note that I don't work on Also, be sure to start a new shell when re-trying |
Still didn't work: $ rm -rf ~/.nvm
$ rm -rf ~/.nvm
$ curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.30.2/install.sh | bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 7750 100 7750 0 0 9531 0 --:--:-- --:--:-- --:--:-- 9532
=> Downloading nvm from git to '/Users/myuser/.nvm'
=> Cloning into '/Users/myuser/.nvm'...
remote: Counting objects: 4344, done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 4344 (delta 0), reused 0 (delta 0), pack-reused 4341
Receiving objects: 100% (4344/4344), 1.09 MiB | 1.88 MiB/s, done.
Resolving deltas: 100% (2544/2544), done.
Checking connectivity... done.
* (HEAD detached at v0.30.2)
master
=> Source string already in /Users/myuser/.bashrc
npm ERR! max depth reached: hapi@>= 8, required by [email protected]
npm ERR! not ok code 0
=> You currently have modules installed globally with `npm`. These will no
=> longer be linked to the active version of Node when you install a new node
=> with `nvm`; and they may (depending on how you construct your `$PATH`)
=> override the binaries of modules installed with `nvm`:
/usr/local/lib
├── [email protected]
├── [email protected]
├── [email protected] -> /Users/m089269/Sites/node-crontab
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├─┬ [email protected] -> /Users/m089269/Sites/hapi-authorization
│ └── hapi@>= 8
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected] -> /Users/m089269/Sites/node-whenever
├── [email protected]
├── [email protected]
└── [email protected]
=> If you wish to uninstall them at a later point (or re-install them under your
=> `nvm` Nodes), you can remove them from the system Node as follows:
$ nvm use system
$ npm uninstall -g a_module
=> Close and reopen your terminal to start using nvm Closed my terminal and reopened it. cd'd to my app dir and $ cd myapp/
avn could not activate node 5.1
$ __avn_debug
avn could not activate node 5.1
error: no plugin passed predicate
avn-nvm: no version matching 5.1 |
So now your install looks correct, but you don't have 5.1 installed If that doesn't work, |
There we go! Works now. Thanks for your help. |
You can see from the output below, i'm unable to successfully
cd
to a dir and have it switch node versions. I tried with both a version I don't have installed via nvm yet (5.0) and one that I do (5.1) and same result.The text was updated successfully, but these errors were encountered: