Skip to content
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

After yarn add. Command -> System cannot find the path specified. WINDOWS 10 #1807

Closed
Alonski opened this issue Nov 14, 2016 · 4 comments
Closed

Comments

@Alonski
Copy link

Alonski commented Nov 14, 2016

Do you want to request a feature or report a bug?

Bug Report
What is the current behavior?
After installing with Yarn I type into my cmd:
ember.
I get back:

"$basedir/../../Users/owner/AppData/Local/Yarn/config/global/node_modules/.bin/ember.cmd"   "$@"
The system cannot find the path specified.

If the current behavior is a bug, please provide the steps to reproduce.

  1. Installed Yarn using Chocolatey via: choco install yarn
  2. Installed ember-cli@1.13.0 via: yarn global add ember-cli@1.13.0
  3. Install finished.
  4. Restart CMD
  5. Insert "ember" into cmd. Hit Enter. CMD closes...
  6. Restart CMD.
  7. Run cmd /k
  8. Run ember
  9. Get error:
"$basedir/../../Users/owner/AppData/Local/Yarn/config/global/node_modules/.bin/ember.cmd"   "$@"
The system cannot find the path specified.

What is the expected behavior?
ember-cli works.
Please mention your node.js, yarn and operating system version.
Operating system: Windows 10 64x
Yarn: 0.16.1
Node: 7.1.0
npm: 3.10.9

@wyze
Copy link
Member

wyze commented Nov 14, 2016

Duplicate #859.

@wyze wyze closed this as completed Nov 14, 2016
@wyze wyze added the duplicate label Nov 14, 2016
@Alonski
Copy link
Author

Alonski commented Nov 14, 2016

This is not the same issue...

@wyze
Copy link
Member

wyze commented Nov 14, 2016

Maybe not exactly, but there are plenty of issues about yarn global add on Windows.

Possibly #1324

@Alonski
Copy link
Author

Alonski commented Nov 14, 2016

From the error message it seems that the problem isn't with global add but with the pathing afterwards. #1324 is closer thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants