-
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
yarn create
fails with scoped packages in 1.9.4
#6266
Comments
Node 10.7.0 |
Same issue here: Yarn 1.9.4
|
When running yarn create, first the package is installed globally, however after installing create was attempting to invoke the binary from within a scope folder that did not exists. The corrects the path resolution to invoke the binary from the actual place it was installed to. fixes yarnpkg#6266
* fix(create): invoke correct path when using scoped package When running yarn create, first the package is installed globally, however after installing create was attempting to invoke the binary from within a scope folder that did not exists. The corrects the path resolution to invoke the binary from the actual place it was installed to. fixes #6266 * Update create.js
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
The binary is being installed to
AppData\Local\Yarn\bin\create-foo
howeveryarn create
is trying to execute a file with the@scope
in the path. This is a regression from 1.7.0 where this worked properly.Please mention your node.js, yarn and operating system version.
Node 8.9.4, Yarn 1.9.4, Windows 7
Possibly related to #6174
The text was updated successfully, but these errors were encountered: