-
-
Notifications
You must be signed in to change notification settings - Fork 398
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
Easing installation of generators? #149
Comments
👍 |
Was pawing around the code, looks like we need to improve Environment.prototype.create |
Improving the UX will always get a huge 👍 from me. Keep the suggestions coming :) |
👍 from me too |
Yes! Please. This would be great. If you get a chance to patch Btw, I noticed you've been asking about how to pull in all of the generators (for the contributor use-case). What we do over in Polymer is have a |
@addyosmani I did this and that for cloning all of the repos. Currently I'm pawing at Update 0: Is this that polymer-all you are referring to? |
^ Changes yo to handle the installation, was wondering if we also need this change in generator also? |
Fixed by setting NODE_PATH |
As of now:
Would it be useful if it's something like:
That would check if there exists a generator-xyz and does a
npm install generator-xyz
The text was updated successfully, but these errors were encountered: