You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[DEP_WEBPACK_DEPRECATION_ARRAY_TO_SET] DeprecationWarning: Compilation.modules was changed from Array to Set (using Array method 'filter' is deprecated)
#430
Closed
dmnsgn opened this issue
Jan 9, 2021
· 0 comments
· Fixed by #431
Do you want to request a feature, report a bug or ask a question?
Deprecation warning
What is the current behavior?
When running with --trace-deprecation,
[DEP_WEBPACK_DEPRECATION_ARRAY_TO_SET] DeprecationWarning: Compilation.modules was changed from Array to Set (using Array method 'filter' is deprecated)
at Set.set.<computed> [as filter] (/Users/my-name/Projects/my-project/node_modules/webpack/lib/util/deprecation.js:85:4)
at getAllModules (/Users/my-name/Projects/my-project/node_modules/svg-sprite-loader/lib/utils/get-all-modules.js:28:8)
at Array.map (<anonymous>)
What is the expected behavior?
No warning
If the current behavior is a bug, please provide the steps to reproduce, at least part of webpack config with loader configuration and piece of your code. The best way is to create repo with minimal setup to demonstrate a problem (package.json, webpack config and your code). It you don't want to create a repository - create a gist with multiple files
If this is a feature request, what is motivation or use case for changing the behavior?
Please tell us about your environment:
Node.js version: v15.5.1
webpack version: 5.11.1
svg-sprite-loader version: 5.2.1
OS type & version: MacOS 10.15
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
The text was updated successfully, but these errors were encountered:
Do you want to request a feature, report a bug or ask a question?
Deprecation warning
What is the current behavior?
When running with --trace-deprecation,
What is the expected behavior?
No warning
If the current behavior is a bug, please provide the steps to reproduce, at least part of webpack config with loader configuration and piece of your code.
The best way is to create repo with minimal setup to demonstrate a problem (package.json, webpack config and your code).
It you don't want to create a repository - create a gist with multiple files
If this is a feature request, what is motivation or use case for changing the behavior?
Please tell us about your environment:
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
The text was updated successfully, but these errors were encountered: