An in-range update of @angular/cli is breaking the build 🚨

[greenkeeper]

The devDependency @angular/cli was updated from 7.3.2 to 7.3.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@angular/cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).
• ✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).

---

Release Notes for v7.3.3

Commits

@schematics/angular (7.3.3)
Commit	Description	Notes
	update karma to version 4	[Closes #13724]
	`findModuleFromOptions` not handling properly different casing in name	[Closes #13714]
	undefined is used as newProjectRoot when none is set	[Closes #13703]
	add file extensions to style prompt
	fixes issue that `ViewEncapsulation` is not being configured when provided	[Closes #13689]
@angular-devkit/build-angular (0.13.3)
Commit	Description	Notes
	improve webpack loader resolution
	minimum threshold

---

Special Thanks

Alan Agius, Amadou Sall, Alan, Charles Lyding, hrocha16

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 7.3.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.