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

[greenkeeper]

The devDependency @compodoc/compodoc was updated from 1.1.10 to 1.1.11.

🚨 View failing branch.

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

@compodoc/compodoc 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 could not complete due to an error (Details).

---

Release Notes for 1.1.11

Features

• feat(i18n): de-DE language #810 Thanks hueppee
• feat(i18n): sk-SK language #830 Thanks Marek Závacký
• feat(routes): support new lazy loading syntax in Angular 8 #819 Thanks Adam Stanley

Bug fixes

• fix(app): max-search-result in options (d759b4f), closes #816 Thanks tzinckgraf
• fix(app): fix path separator replace on Windows during route processing #827 Thanks Adam Stanley
• fix(app): fix unit tests failing on Windows #826 Thanks Adam Stanley

Commits

The new version differs by 110 commits.

• 93f99c3 Finish 1.1.11
• cfb798f Finish 1.1.11
• 647fb3e 1.1.11
• 22ea84e fix(app): refactoring npm ignore
• 45ca8fa fix(app): refactoring / tsconfig file use-case
• 2bbd4e6 fix(app): missing code in files for TSC
• 7e1fa73 fix(app): refactoring tested with namespacing + serve use-case
• d339d40 Update FUNDING.yml
• abcaffb feat(github): stale bot config
• 2eaf83c feat(github): lock bot config
• 522d8e7 feat(app): bump dependencies, remove jest
• 1788267 fix(app): refactoring tested with mocha
• 36ee639 fix(app): refactoring code with TS errors
• 848b025 feat(app): tslint to eslint
• ae8b882 fix(app): refactoring

There are 110 commits in total.

See the full diff

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