An in-range update of babel-loader is breaking the build 🚨

[greenkeeper]

Version 6.4.1 of babel-loader just got published.

Branch	Build failing 🚨
Dependency	babel-loader
Current Version	6.4.0
Type	devDependency

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

As babel-loader is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

• ✅ coverage/coveralls First build on greenkeeper/babel-loader-6.4.1 at 94.81% Details

Release Notes

v6.4.1

🐛 Bug Fix

• Fixed reset of BABEL_ENV when options.forceEnv is used (#420) @nikopavlica

Commits

The new version differs by 2 commits .

• 48325ea 6.4.1
• f3241f8 Fixed reset of BABEL_ENV when options.forceEnv is used (#420)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴