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

yarnpkg alias not working #2534

Open
beac0n opened this issue Jan 23, 2017 · 4 comments
Open

yarnpkg alias not working #2534

beac0n opened this issue Jan 23, 2017 · 4 comments

Comments

@beac0n
Copy link

beac0n commented Jan 23, 2017

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

What is the current behavior?
The alias for yarnpkg is not working:

Installing react and react-dom using yarnpkg...

events.js:160
throw er; // Unhandled 'error' event
^

Error: spawn yarnpkg ENOENT
at exports._errnoException (util.js:1022:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:359:16)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)

If the current behavior is a bug, please provide the steps to reproduce.
OS: Arch Linux
Steps to reproduce:
install yarn, using the AUR: yaourt -S yarn
install create-react-app: sudo yarn global add [email protected]
create a new project with create-react-app: create-react-app testProject

What is the expected behavior?
The alias for yarnpkg should work.

Please mention your node.js, yarn and operating system version.
> $ node --version v7.4.0

> $ yarn --version 0.19.1

Operating System: Arch Linux

Issue in create-react-app repo:
facebook/create-react-app#1429

@Daniel15
Copy link
Member

Daniel15 commented Jan 24, 2017

Maybe it's possible the Arch Linux package doesn't come with a yarnpkg executable, just a yarn one? The Arch package is made by a third party rather than by the Yarn developers, and I'm not quite sure how it's packaged.

@AaronHarris
Copy link
Contributor

I want to chime in, installing using the recommended Windows Installer method on Windows 10 Pro x64 does not seem to add a yarnpkg alias to the PATH. I assume the reason for this is there is only a yarn.cmd file, but no yarnpkg.cmd file in the .bin folder. Would it be sensible to make a windows symlink named yarnpkg.cmd and point it to yarn.cmd?

@Daniel15
Copy link
Member

@AaronHarris - Yeah, Windows only has a yarn.cmd file, not a yarnpkg.cmd file. I think it'd be easiest to add a yarnpkg.cmd file that simply calls yarn.cmd. Would you like to send a pull request?

@AaronHarris
Copy link
Contributor

AaronHarris commented Feb 20, 2017 via email

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

3 participants