-
-
Notifications
You must be signed in to change notification settings - Fork 401
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
Suggestion for installing scoped generator is wrong #518
Comments
PR welcomed, it should be an easy fix on that line: https://github.com/yeoman/environment/blob/566db2a04fec5ab525b63aca0d600ecef5510b9d/lib/environment.js#L343 |
* Fix for issue yeoman/yo#518 * Removed unnecessary '@' filtering in regex * Processed review comments.
Can you guys please close the issues that are fixed |
@buoyantair We try to. But it’s kinda hard to keep track of every single issue within the yeoman organisation. So any help really is appriciated. Even if you just leave a note like to did in here. So, thank you for pointing to this. |
Can scoped generators just be |
Type of issue
Bug
My environment
Windows 10 64-bit
6.1.0
4.5.0
1.8.5
Expected behavior
Attempting to run a scoped generator (e.g.
yo @somescope/somegen
) should tell the user how to install it if it doesn't exist. Thenpm install
suggestion should benpm install @somescope/generator-somegen
.Current behavior
The message is
npm install generator-@somescope/somegen
.Steps to reproduce the behavior
Run
yo @foo/bar
when you do not have@foo/generator-bar
installed.Command line output
The text was updated successfully, but these errors were encountered: