-
Notifications
You must be signed in to change notification settings - Fork 381
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
Generator Blocklist updates #527
Comments
Merged
@eddiemonge, I added those generators to the blacklist in PR #539. |
This was referenced Sep 15, 2015
@hubertburdach can you unpublish or fix https://www.npmjs.com/package/ft-wp please? |
This was referenced Sep 15, 2015
Closing as I opened a duplicate on the generator list page |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are trying to maintain a clean ecosystem. As part of that, the generator list at yeoman.io/generators polls npm for packages with the
yeoman-generator
keyword. It then makes the list available on the site and in the command line search. There are a few entries that aren't valid (we can't really do much for the duplicates without going through every single one in the registry) and we would like to get these fixed.If your module is listed below, can you please update the name to be
generator-yourgeneratorname
and publish that version to npm. It'd be nice if you unpublished the incorrect version or added a deprecation notice and removed theyeoman-generator
keyword so it won't show up in the results.The following generators don't conform to the naming convention at the minimum. Some may not even be generators. If someone wants to ping the owners, that would be nice. They might also be added to the blacklist.
The text was updated successfully, but these errors were encountered: