Simon Boudrias
Simon Boudrias
@arthurvr I think you should hold on until generator-node is done. We can reuse almost everything we're doing over there with this generator.
Do you have a need for easier composability with this specific generator? Also, any chance you'd be willing to spearhead a refresh? And, on the side, we're refactoring [generator-node](https://github.com/yeoman/generator-node/issues/66) to...
welcome is actually run after `prompting` meaning they must just not be in order.
PR welcomed :)
> Alternatively one could also identify if there's ../.bowerrc and fetch the path from there. That's totally what we should do (but with `bower.json`). Using `find-up`, it should be fairly...
cc @eddiemonge
I'd either drop the `--ui` option, or keep two templates. `if/else` inside templates are the worse to maintain.
@dylang what we've been doing in recent generators update is to generate the `package.json` file totally in JS. - The thing is we need logic to decide which packages we...
@kkemple help is always welcome on every aspect of Yeoman. We have a little getting started guide here http://yeoman.io/contributing/
@awayken I think there's a few aspects to consider given Yeoman has a pretty large scope: 1. About the core (yeoman-generator, yo, yeoman-environment), I'd say these are pretty stable and...