-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update babel-loader to the latest version 🚀 #23
base: master
Are you sure you want to change the base?
Conversation
Version 7.1.1 just got published.Update to this version instead 🚀 Release Notes7.1.1🐛 Bug Fix
📝 Documentation
🏠 InternalCommitsThe new version differs by 6 commits.
See the full diff |
Version 7.1.2 just got published.Update to this version instead 🚀 Release Notes7.1.2🐛 Bug Fix
📝 Documentation
🏠 InternalCommitsThe new version differs by 8 commits.
See the full diff |
Version 7.1.3 just got published.Update to this version instead 🚀 Release Notes7.1.3🐛 Bug Fix
CommitsThe new version differs by 7 commits.
See the full diff |
Version 7.1.4 just got published.Update to this version instead 🚀 Release Notes7.1.4🐛 Bug Fix
|
Version 8.0.0-beta.3 just got published.Update to this version instead 🚀 Release Notes8.0.0-beta.3CommitsThe new version differs by 42 commits ahead by 42, behind by 6.
There are 42 commits in total. See the full diff |
Version 7.1.5 just got published.Update to this version instead 🚀 CommitsThe new version differs by 9 commits ahead by 9, behind by 42.
See the full diff |
Version 7.1.0 of babel-loader just got published.
The version 7.1.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.
Release Notes
7.1.0🚀 New Feature
You can now change the babel config while webpack watch or dev-server is running and webpack will correctly recompile all files with babel.
🐛 Bug Fix
📝 Documentation
🏠 Internal
Commits
The new version differs by 13 commits.
d249119
7.1.0
ea9b4d4
Update yarn.lock
7986787
chore(package): update eslint-config-babel to version 7.0.0 (#469)
ee40748
chore(package): update lint-staged to version 4.0.0 (#470)
66784e4
Update to webpack 3 (#471)
8544ffa
Only base cache identifier on babel options from pkg.json (#468)
ea2eafa
Add prettier eslint plugin (#466)
4548169
Add node 8 to test matrix (#467)
d8b73c0
fix(resolve-rc): look for babel in package.json and .babelrc.js (#465)
8d96c1f
Remove outdated examples.
91f2658
Fixed: watch configuration files. (#460)
de2d3f3
Upgrade dependencies
37e63e3
Upgrade find-cache-dir to 1.0 and cross-env to 5.0 (#457)
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 🌴