-
Notifications
You must be signed in to change notification settings - Fork 1
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 webpack to the latest version 🚀 #95
base: master
Are you sure you want to change the base?
Conversation
Version 2.4.0 just got published.Update to this version instead 🚀 Release Notesv2.4.0Highlighted Features:
|
Version 2.4.1 just got published.Update to this version instead 🚀 Release Notesv2.4.1Bugfixes:
|
Version 2.5.0 just got published.Update to this version instead 🚀 Release Notesv2.5.0Bugfixes:
Features:
CommitsThe new version differs by 81 commits0.
There are 81 commits in total. See the full diff |
Version 2.5.1 just got published.Update to this version instead 🚀 Release Notesv2.5.1Bugfixes:
CommitsThe new version differs by 5 commits0.
false See the full diff |
Version 2.6.0 just got published.Update to this version instead 🚀 Release Notesv2.6.0Features:
Bugfixes:
CommitsThe new version differs by 24 commits.
There are 24 commits in total. See the full diff |
Version 2.6.1 just got published.Update to this version instead 🚀 Release Notesv2.6.1Bugfixes:
CommitsThe new version differs by 7 commits.
See the full diff |
Version 3.0.0-rc.1 just got published.Update to this version instead 🚀 Release Notesv3.0.0-rc.1Bugfixes:
|
Version 3.0.0 just got published.Update to this version instead 🚀 Release Notesv3.0.0Changes from 2.6.1 to 3.0.0Features
Bugfixes
Internal changes
Changes from 3.0.0-rc.2 to 3.0.0Bugfixes
Internal changes
CommitsThe new version differs by 44 commits.
There are 44 commits in total. See the full diff |
Version 2.3.3 of webpack just got published.
The version 2.3.3 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 webpack.
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
v2.3.3Bugfixes:
Commits
The new version differs by 2066 commits (ahead by 2066, behind by 66).
ba24c1b
2.3.3
956f618
Fix ProgressPlugin for multi compiler caused by ES6 refactoring
6b209b1
2.3.2
88f2833
Merge pull request #4567 from webpack/bugfix/cheap-source-map
3fca75e
Merge pull request #4565 from webpack/dx/error-description-output-path
c226077
update webpack-sources dependency to fix a bug
2fe82af
Suggest course of action
56d09ab
Merge pull request #4533 from michael-ciniawsky/schema
b5451ef
Merge pull request #4564 from webpack/bugfix/cheap-source-map
22c771f
update webpack-sources dependency to avoid performance issue
4b9b660
2.3.1
d1cf8b4
Merge pull request #4538 from webpack/feature/error-emit-warning
ec46a0d
Merge pull request #4539 from mp4096/master
18566a1
Fixed link to the Traceur repo in README
751fd9b
add stack to non-Error error emitted
There are 250 commits in total. 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 🌴