An in-range update of typedoc is breaking the build 🚨

## The devDependency [typedoc](https://github.com/TypeStrong/TypeDoc) was updated from `0.15.0-0` to `0.15.0`.

🚨 [View failing branch](https://github.com/linkedin/opticss/compare/master...linkedin:greenkeeper%2Fdefault%2Ftypedoc-0.15.0).

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

typedoc 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](https://travis-ci.org/linkedin/opticss/builds/564075690?utm_source=github_status&utm_medium=notification)).

---

Release Notes for Theme Update and More

Features ✨

• Updates included in typedoc-default-themes v0.6.0


• Mixin support (#990)


• Category improvements (#938)


• Default CLI output directory to ./docs (#970)


• Expand JS files if allowJS is enabled (#948)


• Add support for excluding directories and refactor expandInputFiles. (#730)


• Move non-exported types to devdependencies (#1035)


• Support negations in directory excludes (92f0f25)


• Performance: Allow TraverseCallback to bail out early (#1034)

Fixes 🐛

• Reset the state of the comment plugin on conversion start. (#1006)


• Fix handlebars types conflict (#967)


• Fix reference to deprecated handlebars type (#1022)


• Fix bug with the negated/commented exclude patterns (#1025)


• Fix references marked as external if path has dots (#1052)


• Category fixes (#1008)

Documentation help 📖

• Use https in links (#982)


• Add documentation contributing instructions (#973)


• Change some typos and sentence structure in CONTRIBUTING.md (#968)


• Add excludeNotExported to README (#997)

Changed 📦

• Update dependencies (#992) (#1041)


• Update typedoc-default-themes to latest (#993)


• Update typescript to 3.4.x (#1014)


• Update typescript to 3.5.x (#1047)


• Update marked to 0.6.0 to support id generation for headers (#966)


• Update marked to 0.7.0 (e9b28ee)


• npm audit fix (#1019)


• Updated lodash to 4.17.15 to avoid prototype pollution (b328537)


• Reduce reliance on internal TS apis (#949)


• Replace array indexOf checks with includes (#954)


• Remove Grunt (#933)


• Run CI on current Node.js versions (#1053)


• Modify example script permissions (#1011)

Thanks 👏

Thanks to those who identified issues and for the following code contributors:

• @Gerrit0


• @sberthier


• @artentica


• @Beraliv


• @bendtherules


• @jonchardy


• @SamuraiJack


• @igncp


• @fc


• @lddubeau


• @ALiangLiang


• @adidahiya


• @dokmic


• @just-boris


• @nelnog


• @meowtec


• @tsvetomir


• @tusharmath


• @styu


• @ddougan


• @stoically

v0.14.2...v0.15.0

Commits

The new version differs by 30 commits.

• 73a13dd 0.15.0


• 144e667 pin typescript to patch version


• e0cdf64 update dependencies (#1041)


• 92f0f25 Support negations in directory excludes


• b328537 Updated lodash to 4.17.15 (to avoid prototype pollution)


• e9b28ee Update marked to 0.7.0


• 07afa11 fix: references marked as external if path has dots (#1052)


• dfb7207 Revert "Merge branch 'master' into master"


• 29df793 Merge branch 'master' into master


• dc3c6f9 fix(package): update to typescript 3.5.x (#1047)


• a2d3704 Merge pull request #1 from TypeStrong/master


• ae67b72 run CI on current Node.js versions (#1053)


• 9d54cc6 v0.15.0


• 968da56 Fix tests


• eb3cc11 Ran install

There are 30 commits in total.

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:

Start with the Greenkeeper failing branch and the linked Travis CI build to identify why typedoc 0.15.0 breaks the project build. The issue names no repository file or failing test, so inspect the typedoc dependency configuration and CI output; done means the dependency update is applied and the build passes.

Written by the indexing model from the issue text.