Yeoman custom generator
yeoman
Solution
What is the workflow for testing a generator?
I'll be working on this in the next couple of days for generator-angular. You can track my progress on Github. Unfortunately, there aren't too many examples yet because of the transition from one `yeoman` command to using `yo` alongside `bower` and `yo`. I imagine there will be some level of unit testing on the `Generator.prototype.method`, as well as E2E testing that involves writing bash scripts to run `yo`, `npm`, `bower`, and `grunt`.
Has the generator framework changed at all with the beta of yo 1.0? Have there been breaking changes?
In my experience porting over generator-angular, I haven't seen too many changes. There is a new, optional simplified API, which may be useful.
How does a generator register itself with the global `yo` binary?
The answer right now is that it doesn't. You install/use generators in a project directory. I somehow had it working due to an errant symlink, but that's not the recommended way of doing it.
Problem
I would like to make a custom generator with the latest version of yeoman, but I'm having some difficulty. I've been digging around various sources of documentation and examples (like the webapp and angular generators), but I still have a few questions. What is the workflow for testing a generator? If I have one project that is the generator itself, do I keep making new directories to run `yo my-generator`? Has the generator framework changed at all with the beta of `yo` 1.0? Have there been breaking changes? How does a generator register itself with the global `yo` binary? Thanks.