An in-range update of babel-plugin-add-module-exports is breaking the build 🚨

[greenkeeper[bot]]

The devDependency babel-plugin-add-module-exports was updated from 1.0.0 to 1.0.1.

🚨 View failing branch.

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

babel-plugin-add-module-exports 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/feathersjs-ecosystem/feathers-reactive/builds/520848696?utm_source=github_status&utm_medium=notification)).

---

Commits

The new version differs by 5 commits.

• 38e2e68 v1.0.1
• df47a0a [patch] Add module.exports to files using es3 member literals
• e8e5be0 docs: tweaks [ci skip]
• d0001d5 docs(README): add webpack notes(refs #68) & tweaks [ci skip]
• 753d945 chore: tweak postversion script [ci skip]

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 Bot :palm_tree:

[greenkeeper[bot]]

After pinning to 1.0.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper[bot]]

• The devDependency babel-plugin-add-module-exports was updated from 1.0.0 to 1.0.2.

Your tests are still failing with this version. Compare changes