- chore: optimize npm package and reduce unpacked size: 31 kB -> 9 kB
- docs: update readme
- docs: update readme
- fix: remove needless double new lines in console output when the
verboseoption is enabled - chore: add Community Standards files
- chore: update dev packages
- test: remove the test strategy for node versions 12.x on GitHub to allows use the latest dev packages. The plugin is still compatible with node 12.x.
- test: add the test strategies for node versions 18.x and 20.x on GitHub
- test: refactor test utilities
- test: add tests for alternative way using the html-bundler-webpack-plugin
- docs: update readme
- fix: fix interface syntax in TS
- fix:
optionsin constructor now is optional parameter in types for TS.
- fix: correctly export types for TS when used CommonJS
- chore: update dev packages
- docs: update readme
- docs: update readme
-
BREAKING CHANGE: reverted default behavior as in
v0.8.1- remove empty scripts before other plugins will be called. This change is needs for properly work of the vast majority of webpack plugins.For compatibility with
v0.8.2 - v0.8.4, if you have an issue, use newstageoption with the value:new RemoveEmptyScriptsPlugin({ stage: RemoveEmptyScriptsPlugin.STAGE_AFTER_PROCESS_PLUGINS, })
-
feat: add new
stageoption. Webpack's plugins use different stages for their functionality. For properly work other plugins can be specified thestagewhen should be removed empty scripts: before or after processing of other webpack plugins.
For example, using@wordpress/dependency-extraction-webpack-pluginthe empty scripts must be removedafterprocessing all plugins. Usingwebpack-manifest-pluginthe empty scripts must be removedbeforeprocessing other plugins. -
chore: update packages
-
test: add the test for using with webpack-manifest-plugin
-
docs: update readme
- fix: fix last stable version of ansis in package.json to avoid issues in dependency
- docs: update readme
- fix: keep extracted wordpress dependencies, #9
- test: refactor tests
- chore: update npm packages
- fix: add supports for TypeScript
- chore: update packages
- docs: update readme
- feat: add new option
removeto define custom RegExp for generated assets that must be removed - chore: update packages
- feat: add color verbose output via ANSI color library - ansis
- feat: add the test case for styles imported from javascript
- feat: add new option
enableto enable / disable the plugin, e.g. by development - feat: add supports of
RegExpfor optionextensions - chore: remove deprecated option
silent, useverboseto show process information (no braking change) - chore: add GitHub workflow + codecov
- chore: update packages
- docs: update readme
- fix: the issue infinite recursion by collect of resources from dependency modules by usage in react app some big components with many thousands dependencies
- chore: deprecate the
silentoption, it will be removed on Jun 30, 2021. Use optionverbose: trueto show in console each removed empty file. Defaults,verbose: false. - fix: issue
Maximum call stack size exceededin all cases, for example, by usage the webpack settingoptimization.concatenateModules: trueand:- import react
- import redux
- webpack setting
externals.jquery: 'jQuery'or other external libs
- fix: the issue if first in webpack entries are a styles and then a scripts
- feat: improve the option
ignore:- it can be the array of string or RegExp
- added default value of
ignoreas['/node_modules/']to ignore resources fromnode_modulespath
- fix: the error:
Maximum call stack size exceededwith webpack settingoptimization.concatenateModules: trueand usage in script imports fromreactandredux - test: add the test case for single style without a scripts in webpack config
- test: add silent mode in tests to suppress output log info in the console
- chore: update packages
- fix: BREAKING CHANGE in Webpack 5: no more changes should happen to
Compilation.assets - refactor: update code according Webpack 5 API
- chore: update packages
The fork of original webpack-fix-style-only-entries (ver. 0.6.0) for support only Webpack 5 and above. The Webpack 4 is no longer supported.
-
feat: considers the use hash after the .js and .mjs extension in file format like
.js?[hash]or.mjs?[hash]. The idea and requirement belong to MatiasMorici from PR -
fix: in Webpack 5 fixed deprecation messages:
- DEP_WEBPACK_CHUNK_HAS_ENTRY_MODULE
- DEP_WEBPACK_CHUNK_ENTRY_MODULE
- DEP_WEBPACK_DEPRECATION_ARRAY_TO_SET
- DEP_WEBPACK_MODULE_INDEX
-
fix: integration test script for using with Webpack 5
-
fix: issue using
terser-webpack-pluginis generated the needless filevendor.js.LICENSE.txtin the production testvendor+multi-js-entry-css-entry -
docs: corrected module structure in README.md
-
chore: update packages
Being overly careful here, this version is not breaking for almost all the existing users. It could possibly break in some edge cases, since it changes how modules are collected (from global to one each compilation) or if you have a workaround for a working webpack multi configuration.
- BREAKING POSSIBLY: Use a dedicated cache for every compilation (Prevent arbitrary files deletion when using Webpack with multi configurations) (PR #39)
- BREAKING CHANGE: added styl and sass to default extensions (247a5c)
- fix: for #23 (37d350)
- fix: for #24 (d92bec)
- chore: add LICENSE.txt (220e20)
- feat: add support for module js files (PR #21)