Remove npm warnings when creating a new project.

[LoicPoullain]

When creating a new project, we get unnecessary warnings about the description, repository and license.

This could be removed.

[bbeesley]

Happy to look into this, but there are a couple of options I guess, either modify the package.json templates to populate those fields (repository isn't really possible unless the user inputs it). Not sure this is totally sensible anyway since the user should really enter these at some point.

A better option might be to just mute the warns on that initial install. This is super easy to do with npm, but very difficult with yarn (it's "warn" method writes direct to process.stdout even with the silent option enabled). For that I'd have to write a processor to read from the child process stdout, filter out the warnings, and pass the non warning messages back out to the main process stdout.

Which route would you prefer going down?

[LoicPoullain]

Good catch for the yarn issue!

I'd prefer to go for the first one because it will be easier to maintain in the future. The less code we have to deal with in the framework, the better it is. Child processes might also be harder to unit test.

Would it work if we add the repository field but with an empty string?

[LoicPoullain]

Fixed in v1.10.0