-
Notifications
You must be signed in to change notification settings - Fork 4
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
An in-range update of webpack is breaking the build 🚨 #15
Comments
Version 2.4.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv2.4.1Bugfixes:
|
Version 2.5.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 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.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv2.5.1Bugfixes:
CommitsThe new version differs by 5 commits0.
false See the full diff |
Version 2.6.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 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.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv2.6.1Bugfixes:
CommitsThe new version differs by 7 commits.
See the full diff |
Version 2.4.0 of webpack just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As webpack 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 💪
Status Details
✅ coverage/coveralls First build on greenkeeper/webpack-2.4.0 at 84.173% Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes
v2.4.0Highlighted Features:
import()
now allows to configure a chunk namerequire.ensure
has a error callbackFeatures:
warningsFilter
to stats options to filter warnings__webpack_chunkname__
toExtendedAPIPlugin
NamedChunksPlugin
which allows to set chunk id, i. e. to chunk namerequire.ensure
import()
Bugfixes:
Commits
The new version differs by 252 commits .
0cbd8fd
2.4.0
ab22702
Merge pull request #4507 from ts-webpack/refactor/clean-code
e787452
Merge pull request #4700 from webpack/bug/future-var-declaration
98153f5
Merge pull request #4706 from webpack/test/parser-coverage
52f2daf
add test cases and fix a bug
e4b8833
improve code coverage
3afe67d
add parser prewalking to capture scope
0990915
spacing
d8a8bd3
deprecate string option instead of removing it
dbc40e8
Merge pull request #4698 from simon04/examples-source-map
0ef0581
Add example demonstrating all source-map variants
a822784
Merge pull request #4696 from webpack/bugfix/parser-refactoring
ba3688a
fixes misstake while es6 refactoring, add support for other variable declarations
07f6281
fix: typos and variables/function misuse
52055ba
refactor: dead code elimination
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 🌴
The text was updated successfully, but these errors were encountered: