-
Notifications
You must be signed in to change notification settings - Fork 1
An in-range update of webpack is breaking the build 🚨 #30
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
Comments
After pinning to 4.10.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 4.11.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.11.1Features
Bugfixes
|
Version 4.12.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.12.0Features
Bugfixes
CommitsThe new version differs by 53 commits.
There are 53 commits in total. See the full diff |
Version 4.12.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv4.12.1Bugfixes
Internal changes
CommitsThe new version differs by 55 commits.
There are 55 commits in total. See the full diff |
Version 4.12.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.12.2Bugfixes
CommitsThe new version differs by 74 commits.
There are 74 commits in total. See the full diff |
Version 4.13.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv4.13.0Features
Bugfixes
CommitsThe new version differs by 52 commits.
There are 52 commits in total. See the full diff |
Version 4.11.0 of webpack was just published.
webpack
This version is covered by your current version range and after updating it in your project the build failed.
webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
Release Notes
v4.11.0Features
reportProgress
inafterEmit
Bugfixes
Commits
The new version differs by 87 commits.
e2fe200
4.11.0
b1a640e
Merge pull request #7479 from webpack/fix/5153
b5b1e86
Merge pull request #7478 from webpack/fix/5889
aa6de57
Ensure static and dynamic imports use the same binding
348057f
Add a test case to invalidate #5889
5653732
Merge pull request #7476 from sandersn/fix-template-tag-syntax
c971073
Fix template tag syntax
19389b7
Merge pull request #7447 from xtuc/fix-wasm-check-for-invalid-signatures
78b3193
add checkWasmTypes flag, enabled it only in production
bc6b5b0
Merge pull request #7444 from MLoughry/prefetch-from-entry
c65d164
fix test case
591521b
support node.js 10 and 8
c77ec39
revert afterStartup and trigger prefetch before startup
dc0e1ec
Merge branch 'master' into prefetch-from-entry
db668b7
move fake document to ConfigTestCases
There are 87 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: