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

Suggestion for installing scoped generator is wrong #518

Closed
Jameskmonger opened this issue Apr 27, 2017 · 4 comments
Closed

Suggestion for installing scoped generator is wrong #518

Jameskmonger opened this issue Apr 27, 2017 · 4 comments

Comments

@Jameskmonger
Copy link

Type of issue

Bug


My environment

  • OS version/details: Windows 10 64-bit
  • Node version: 6.1.0
  • npm version: 4.5.0
  • Version of yo : 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. The npm install suggestion should be npm 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

λ yo @foo/bar
Error @foo/bar

You don’t seem to have a generator with the name “@foo/bar” installed.
But help is on the way:

You can see available generators via npm search yeoman-generator or via http://yeoman.io/generators/.
Install them with npm install generator-@foo/bar.

To see all your installed generators run yo without any arguments. Adding the --help option will also show subgenerators.

If yo cannot find the generator, run yo doctor to troubleshoot your system.
@SBoudrias
Copy link
Member

SBoudrias pushed a commit to yeoman/environment that referenced this issue May 3, 2017
* Fix for issue yeoman/yo#518

* Removed unnecessary '@' filtering in regex

* Processed review comments.
@elevenpassin
Copy link
Contributor

Can you guys please close the issues that are fixed

@mischah
Copy link
Member

mischah commented Nov 3, 2017

@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.

@rodoabad
Copy link

Can scoped generators just be @foo/generator?

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

No branches or pull requests

5 participants