An in-range update of source-map-support is breaking the build 🚨

Nobody has claimed this yet.

## The dependency [source-map-support](https://github.com/evanw/node-source-map-support) was updated from `0.5.12` to `0.5.13`.

🚨 [View failing branch](https://github.com/linkedin/opticss/compare/master...linkedin:greenkeeper%2Fdefault%2Fsource-map-support-0.5.13).

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

source-map-support is a direct dependency of this project, and **it is very likely causing it to break**. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/linkedin/opticss/builds/565894446?utm_source=github_status&utm_medium=notification)).

---

Commits

The new version differs by 4 commits.

• 4a9c45d 0.5.13


• c4453fd Update built files


• bfc73f9 Merge pull request #249 from evanw/LinusU-patch-1


• 4852362 Tweak regex in retrieveSourceMapURL

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 failing Travis CI build and the linked Greenkeeper comparison for source-map-support 0.5.13. Review the four upstream commits and identify why the dependency update breaks the project; done means the build passes with a compatible dependency version.

Written by the indexing model from the issue text.