┌─────────────────────────────────────────────────────────────┐
│ │
│ There is a new version of expo-cli available (4.0.17). │
│ You are currently using expo-cli 3.0.2 │
│ Run npm install -g expo-cli to get the latest version │
│ │
└─────────────────────────────────────────────────────────────┘
OK, so it looks like a previous installation of node/npm installed the expo command to /usr/local/bin/expo and the rest of the package to /usr/local/lib/node_modules/expo-cli. The current version of npm looks like it’s installing the expo command to the .npm-global/bin directory inside your home directory.
I am not sure what would have caused this difference in the installation locations.
Can you run ls -l /Users/alexander/.npm-global/bin/expo to see where the symlink is pointing? I suspect it’s to somewhere in your home directory instead of /usr/local/lib/node_modules/
To get it working, you’ll need to either convince the current npm to install stuff under /usr/local or the safer option: add /Users/alexander/.npm-global/bin to your PATH, but it must come somewhere before /usr/local/bin.
To get it working, you’ll need to either convince the current npm to install stuff under /usr/local or the safer option: add /Users/alexander/.npm-global/bin to your PATH , but it must come somewhere before /usr/local/bin .
Shall I add
export PATH=“/Users/alexander/.npm-global/bin:$PATH” ?
Please help me with the same issue.
I ran ls -l /usr/local/bin/expo
lrwxr-xr-x 1 bilalhaidermakki admin 40 Dec 24 19:42 /usr/local/bin/expo → …/lib/node_modules/expo-cli/bin/expo.js
ran npm bin -g
/usr/local/Cellar/node/15.5.1/bin
(not in PATH env variable)
Will export PATH=“/usr/local/Cellar/node/15.5.1/bin:$PATH” fix my issue also?