An in-range update of magic-string is breaking the build 🚨

## The dependency [magic-string](https://github.com/rich-harris/magic-string) was updated from `0.25.3` to `0.25.4`.

🚨 [View failing branch](https://github.com/benjamn/reify/compare/master...benjamn:greenkeeper%2Fmagic-string-0.25.4).

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

magic-string 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/benjamn/reify/builds/591551239?utm_source=github_status&utm_medium=notification)).

---

Commits

The new version differs by 3 commits.

• 51e7f5f -> v0.25.4


• 68fcedc Merge pull request #163 from ggoodman/fix-clone-intro-outro


• 93d0e4b Clones intro and outro of MagicString

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 by opening the linked failing Travis CI build and comparing the magic-string 0.25.3 to 0.25.4 update with the three listed upstream commits. Trace the reported build failure in the repository, then verify that the project builds successfully with a compatible dependency version.

Written by the indexing model from the issue text.