-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]Cannot add global nodemon with yarn #3531
Comments
Hi, we're having issues with this version of yarn, 0.24.6, and nodemon also. Reverting back to 0.24.4 solves the problem, but otherwise yarn cannot find nodemon. With the exact same 0.24.6
0.24.4
Reference: |
You need to add @djenriquez, there are no changes between 0.24.4 and 0.24.6 that touch global or path https://github.com/yarnpkg/yarn/commits/0.24-stable. |
Closing due to inactivity. |
Like what @bestander said add yarn/bin to your system PATH, If you are planning to migrate from NPM to Yarn, make sure to add its path to the System variables to avoid any future error i.e 'name' not recognized |
I'd like to reopen this issue, I'm still having this problem. My $ yarn global bin
/usr/local/bin
$ echo $PATH
/Users/andrew/.virtualenvs/cdt/bin:/Users/andrew/.bin:/usr/local/bin:/usr/bin:/bin:...
# shortened for brevity
# note /usr/local/bin is the third item
$ yarn global add nodemon
yarn global v1.7.0
[1/4] 🔍 Resolving packages...
[2/4] 🚚 Fetching packages...
[3/4] 🔗 Linking dependencies...
[4/4] 📃 Building fresh packages...
success Installed "nodemon@1.17.5" with binaries:
- nodemon
✨ Done in 5.08s.
$ nodemon
zsh: command not found: nodemon
$ which nodemon
nodemon not found |
I am using the latest stable version of yarn 0.24.6 for windows
Do you want to request a feature or report a bug?
Recently, I used yarn to install nodemon on my windows 10x64,
What is the current behavior?
$ yarn add global nodemon yarn add v0.24.6 [1/4] Resolving packages... [2/4] Fetching packages... warning fsevents@1.1.1: The platform "win32" is incompatible with this module. info "fsevents@1.1.1" is an optional dependency and failed compatibility check. Excluding it from installation. [3/4] Linking dependencies... [4/4] Building fresh packages... success Saved lockfile. success Saved 143 new dependencies.
If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
I expected it would have install nodemon globally like npm, but apparently it isn't.
I have tried to remove the nodemon package with
yarn remove global nodemon
and installed it again but nothing changed.The package works normally with npm method.
Please mention your node.js, yarn and operating system version.
Latest node.js
Latest yarn
Windows 10 x64 with vscode.
The text was updated successfully, but these errors were encountered: