An in-range update of @angular-devkit/build-ng-packagr is breaking the build 🚨

[greenkeeper]

The devDependency @angular-devkit/build-ng-packagr was updated from 0.13.3 to 0.13.4.

🚨 View failing branch.

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

@angular-devkit/build-ng-packagr 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/travis-ci/push: The Travis CI build failed (Details).

---

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 0.13.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

• The devDependency @angular-devkit/build-ng-packagr was updated from 0.13.4 to 0.13.5.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

[greenkeeper]

• The devDependency @angular-devkit/build-ng-packagr was updated from 0.13.5 to 0.13.6.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

[greenkeeper]

• The devDependency @angular-devkit/build-ng-packagr was updated from 0.13.6 to 0.13.7.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

[greenkeeper]

• The devDependency @angular-devkit/build-ng-packagr was updated from 0.13.7 to 0.13.8.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀