Update @angular/cli to the latest version 🚀

[greenkeeper]

Version 1.3.0 of @angular/cli just got published.

Dependency	@angular/cli
Current Version	1.3.0-rc.0
Type	devDependency

The version 1.3.0 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of @angular/cli.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[coveralls]

Coverage remained the same at 92.857% when pulling 027c410 on greenkeeper/@angular/cli-1.3.0 into 70d68c2 on master.

[greenkeeper]

Version 1.3.1 just got published.

Update to this version instead 🚀

Release Notes

v1.3.1

Bug Fixes

• @angular/cli: ng completion inside of ng app folders warns but does not produce output (5752d18), closes #6343
• @angular/cli: fix ever increasing lazy chunk name counter (da2c71a)
• @angular/cli: fix problem of SuppressPlugin in case entryFiles type is string (#7393) (310dd81)
• @angular/cli: Revert change to config reading (aa9103a)
• @angular/cli: Update bootstrap test based upon beta (20fd846), closes #7358
• @ngtools/webpack: don't use src dir as a resource (cef613c), closes #6238 #6959