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 :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/Chamberlab/datadeck-nwjs/builds/201800427)
Release Notesv6.3.1
🐛 Bug Fix
The new forceEnv options wasn't working as expected (#379) @chrisvasz
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 6.3.1 of babel-loader just got published.
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 :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/Chamberlab/datadeck-nwjs/builds/201800427)Release Notes
v6.3.1forceEnvoptions wasn't working as expected (#379) @chrisvaszCommits
The new version differs by 5 commits .
01308ff6.3.1571034dUpdate yarn.lockb9b38e4Update CHANGELOG.mdfdf0184Apply forceEnv option to Babel transformation (#379)08ef070Add node 0.12 for webpack 1 (#378)See the full diff.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: