-
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 @scope doesnt work as expected #6233
Comments
I don't think we ever supported |
@arcanis sure, pull-request is almost ready |
@arcanis unfortunately there are no existing tests for "create" command. is it okay to submit fix without tests? |
That should be fine for |
This one works as it should: yarn create @scope/name => @scope/create-name There were problems when name was omitted: Before: yarn create @scope => create- yarn create @scope/ => @scope/create- After: yarn create @scope => @scope/create yarn create @scope/ => @scope/create Fixes yarnpkg#6233
This one works as it should: yarn create @scope/name => @scope/create-name There were problems when name was omitted: Before: yarn create @scope => create- yarn create @scope/ => @scope/create- After: yarn create @scope => @scope/create yarn create @scope/ => @scope/create Fixes yarnpkg#6233
This one works as it should: yarn create @scope/name => @scope/create-name There were problems when name was omitted: Before: yarn create @scope => create- yarn create @scope/ => @scope/create- After: yarn create @scope => @scope/create yarn create @scope/ => @scope/create Fixes yarnpkg#6233
* fix(cli-create): fix scoped creation This one works as it should: yarn create @scope/name => @scope/create-name There were problems when name was omitted: Before: yarn create @scope => create- yarn create @scope/ => @scope/create- After: yarn create @scope => @scope/create yarn create @scope/ => @scope/create Fixes #6233 * refactor(cli-create): make parsePackageName more robust and add tests * refactor(cli-create): add missing typyings
What is the current behavior? it is also steps to reproduce
What is the expected behavior? npm's one is an expected behaviour
Please mention your node.js, yarn and operating system version.
The text was updated successfully, but these errors were encountered: