chore: remove angular-cli from node modules of new projects - #731

I'm sure someone has already thought of this, just dropping a note here on the slight chance it is not yet come up. I expect that CLI will continue to be improved and evolve over time. Probably in a mostly backward-compatible way, but it is unlikely to remain 100% perfectly compatible at all times. The traditional solution for this with many other tools in the node ecosystem is take a dependency in a specific project on a specific version of a tool used for building or development. For example, gulp, grunt, karma, broccoli, many hundreds of others work this way. The globally installed tool acts only as a hook to run a version controlled project specific installation. This makes it possible for individual projects to keep working without accidental breakage, even as a tool they depend on continues to evolve. I am guessing something similar will work for angular-cli, but this PR made me wonder if maybe that has not yet been addressed.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}