An in-range update of webpack is breaking the build π¨
greenkeeper opened this issue Β· 4 comments
The devDependency webpack was updated from 4.22.0
to 4.23.0
.
π¨ View failing branch.
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
- β continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Release Notes for v4.23.0
Features
- add
watchMode
flag to Compiler to be able to detect watch mode in plugins - Prefer chunk names of entrypoints when merging chunks
- add
removedFiles
property to Compiler to detect removed files
Bugfixes
- publish declarations to npm
- upgrade
@webassemblyjs/*
for bugfix - fix crash when using a side-effect-free wasm module in production mode
Internal changes
- test on node.js 12
- fix memory leak in test suite
Commits
The new version differs by 35 commits.
a4feb6e
4.23.0
298fa4c
Merge pull request #8266 from ljqx/wasm-finalize-exports-fix
035ceb6
force travis rerun
735b4aa
Merge pull request #8182 from xtuc/ci-node-nightly
6844c75
add test
8256249
longer timeouts for Compiler test
f7ff913
use latest node 12 nightly
1c44f95
fix bug where module is referenced which is not in the graph
98d077d
order values with different types correctly
f5e45be
also export WebAssembly.Global when reexporting globals
b22f027
Update tests for new WebAssembly.Global API
edcadbb
ci: add node 11
91755a2
Merge pull request #8265 from webpack/ci/fix-memory-issue
523ddd7
avoid memory leak
48656d2
[WasmFinalizeExportsPlugin] check if
ref
is null before using it
There are 35 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 π΄
After pinning to 4.22.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
- The
devDependency
webpack was updated from4.23.0
to4.23.1
.
Your tests are still failing with this version. Compare changes
Release Notes for v4.23.1
Bugfixes
- add space when replacing expression with constant
- i. e. for code like
return'development'===process.env.NODE_ENV&&'foo'
- i. e. for code like
- The
devDependency
webpack was updated from4.23.1
to4.24.0
.
Your tests are still failing with this version. Compare changes
Release Notes for v4.24.0
Features
- allow to pass no dependencies to DefinePlugin runtime value
DefinePlugin.runtimeValue(() => {...}, true)
is always evaluated
- add
module
argument toDefinePlugin.runtimeValue
Bugfixes
- update webassemblyjs dependency
- fix bug when using entry names that look like numbers with HMR
Commits
The new version differs by 24 commits.
9e397b5
4.24.0
56846fb
Merge pull request #8319 from webpack/update-dev-tools
2a440fe
Update development tools
c832cb7
Merge pull request #8306 from FranckFreiburger/master
a640cd0
- update/enhance the test
7dc8e51
pass { module } instead of module
8be0485
Merge pull request #8307 from xtuc/chore-bump-webassemblyjs17
2eff6aa
chore: bump webassemblyjs
a093cfa
run eslint --fix
979320e
- add a test for PR#8306
2b0025a
add module argument to DefinePlugin.runtimeValue functions
7076c05
Merge pull request #8299 from JackyTianer/master
145b719
remove test script in package.json
d66cce2
add test case by this change
536e271
Merge pull request #8295 from HarlemSquirrel/examples-readme-20181028
There are 24 commits in total.
See the full diff
fixed