Update dependency webpack to v4.26.0 #93
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.17.1->4.26.0By merging this PR, the below vulnerabilities will be automatically resolved:
Release Notes
webpack/webpack (webpack)
v4.26.0Compare Source
Features
Note: While they are officially backward-compatible, it can still happen that a new bugs occurs with terser, which break your production builds. Make sure to validate your production builds after upgrading to this version. (Note that it's always a good idea to test your output assets before deploying.)
If you want to report bugs to terser (https://github.com/terser-js/terser), please provide a minimal repro case with minimized and non-minimized code. You can configure webpack to generate non-minimized code in production mode by setting
optimization.minimize: false. When reporting a bug to terser, best report a repro case which doesn't require running webpack and is reproducible with only the terser command line.See
optimization.minimizersconfiguration option to switch back to uglify-es or provide additional minimize options for terser.v4.25.1Compare Source
Bugfixes
v4.25.0Compare Source
Features
formatoption toDllPluginto allow generating formated manifest jsonProgressPluginto add and remove informationBugfixes
.mjsv4.24.0Compare Source
Features
DefinePlugin.runtimeValue(() => {...}, true)is always evaluatedmoduleargument toDefinePlugin.runtimeValueBugfixes
v4.23.1Compare Source
Bugfixes
return'development'===process.env.NODE_ENV&&'foo'v4.23.0Compare Source
Features
watchModeflag to Compiler to be able to detect watch mode in pluginsremovedFilesproperty to Compiler to detect removed filesBugfixes
@webassemblyjs/*for bugfixInternal changes
v4.22.0Compare Source
Features
&&and||expressionsBugfixes
Performance
v4.21.0Compare Source
Features
output.libraryTarget: "amd-require"which generates a AMDrequire([], ...)wrapper instead of adefine([], ...)wrapperoutput.library, which exposes the library to a subpropertyBugfixes
__webpack_require__.eis used at runtime but is not defined in the bundleglobaltypePerformance
v4.20.2Compare Source
Bugfixes
export defaultin concatenated modulesv4.20.1Compare Source
Bugfixes
libraryTarget: "amd"without library namev4.20.0Compare Source
Bugfixes
Internal changes
v4.19.1Compare Source
Bugfixes
import()withtarget: "electron-main"uses correct path separator on windows(This fixes a problem with filemappings in vscode)
devtool: "source-map"and variants generate SourceMaps when output file is.mjsbrowserfield as object is used when usingtarget: "electron-renderer"export defaultare preservedexternalsvalue, now works correctly as documentedv4.19.0Compare Source
Bugfixes
v4.18.1Compare Source
Bugfixes
v4.18.0Compare Source
Features
v4.17.3Compare Source
Bugfixes
v4.17.2Compare Source
Bugfixes