Update @angular-devkit/build-ng-packagr to the latest version 🚀

[greenkeeper]

The devDependency @angular-devkit/build-ng-packagr was updated from 0.8.5 to 0.10.0.

This version is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

---

Find out more about this release.

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]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

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

Update to this version instead 🚀

[greenkeeper]

---

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

---

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

Update to this version instead 🚀

[greenkeeper]

---

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

---

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

Update to this version instead 🚀

[greenkeeper]

---

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

---

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

Update to this version instead 🚀