Skip to content

Conversation

@greenkeeper
Copy link
Contributor

@greenkeeper greenkeeper bot commented Feb 14, 2017

Version 6.3.0 of babel-loader just got published.

Dependency babel-loader
Current Version 6.2.10
Type devDependency

The version 6.3.0 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of babel-loader.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.


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 and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

@coveralls
Copy link

coveralls commented Feb 14, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling 69edc7c on greenkeeper/babel-loader-6.3.0 into 5f30cc2 on master.

@kumar303 kumar303 merged commit f18db29 into master Feb 14, 2017
@greenkeeper greenkeeper bot deleted the greenkeeper/babel-loader-6.3.0 branch February 14, 2017 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants