Open greenkeeper[bot] opened 7 years ago
Your tests are passing again with this version. Explicitly upgrade to this version π
forceEnv
options wasn't working as expected (#379) @chrisvasz
Your tests are passing again with this version. Explicitly upgrade to this version π
forceEnv
was interfering with regular environment handlingYour tests are passing again with this version. Explicitly upgrade to this version π
The new version differs by 16 commits .
36db87b
6.4.0
da6201a
Update CHANGELOG.md for 6.4.0
ca3318b
Optimize code after merge of #398
cd10945
Update yarn.lock
a8fd06e
Sort package.json
1fbbdf3
added metadata passing from babel to webpack (#398)
2fbcc01
document globalOptions (#365)
9ea739f
Docs: change babel-preset-es2015 to babel-preset-env (#404) [skip ci]
931c619
Update CHANGELOG.md
2db79de
6.3.2
b71a437
Fix forceEnv (#384)
01308ff
6.3.1
571034d
Update yarn.lock
b9b38e4
Update CHANGELOG.md
fdf0184
Apply forceEnv option to Babel transformation (#379)
There are 16 commits in total. See the full diff.
Your tests are passing again with this version. Explicitly upgrade to this version π
The new version differs by 18 commits .
48325ea
6.4.1
f3241f8
Fixed reset of BABEL_ENV when options.forceEnv is used (#420)
36db87b
6.4.0
da6201a
Update CHANGELOG.md for 6.4.0
ca3318b
Optimize code after merge of #398
cd10945
Update yarn.lock
a8fd06e
Sort package.json
1fbbdf3
added metadata passing from babel to webpack (#398)
2fbcc01
document globalOptions (#365)
9ea739f
Docs: change babel-preset-es2015 to babel-preset-env (#404) [skip ci]
931c619
Update CHANGELOG.md
2db79de
6.3.2
b71a437
Fix forceEnv (#384)
01308ff
6.3.1
571034d
Update yarn.lock
There are 18 commits in total. See the full diff.
Version 6.3.0 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 a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you itβs very likely also breaking them. I recommend you give this issue a very high priority. Iβm sure you can resolve this :muscle:
Status Details
- β **coverage/coveralls** First build on greenkeeper/babel-loader-6.3.0 at 12.808% [Details](https://coveralls.io/builds/10141425) - β **ci/circleci** Your tests passed on CircleCI! [Details](https://circleci.com/gh/leecade/fe/193?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link) - β **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/leecade/fe/build/1.0.214)Release Notes
v6.3.0forceEnv
(#368) @moimaelAllow to override BABEL_ENV/NODE_ENV at loader-level. Useful for isomorphic applications which have separate babel config for client and server.
Commits
The new version differs by 10 commits .
877e956
6.3.0
4b3bafa
FS caching improvements (#375)
0b19a6d
Update loader-utils dependecy to ^0.2.16 (#371)
15881f4
Add env query parameter. (#368)
e9e3702
Update yarn.lockk
707f31c
chore(package): update eslint-config-babel to version 6.0.0 (#360)
5657f48
chore(package): update eslint-config-babel to version 5.0.0 (#359)
757002a
Remove plugin-babel (#358)
a7e16da
Update eslint-config-babel to the latest version π (#357)
3900952
Update CHANGELOG.md
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: