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
Do you want to request a feature, report a bug or ask a question?
Bug
What is the current behavior?
WARNING in ./src/svg/icon-cart.svg
Module Warning (from ./node_modules/svg-sprite-loader/lib/loader.js):
svg-sprite-loader exception. Some loaders will be applied after svg-sprite-loader in extract mode
@ ./src/svg/sprite.js 3:0-26
What is the expected behavior?
No warning. It works, so why complain?
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.
This suggests it wants to be the FIRST entry, not the last (or latest)... But even so, why is this made into a problem in the first place? Why does this plugin need to complain about its position in the configuration??
Please tell us about your environment:
Node.js version: 10.16.3
webpack version: 4.16.5
svg-sprite-loader version: 4.2.1 ~ 6.0.0
OS type & version: Windows 10 21H2
The text was updated successfully, but these errors were encountered:
Do you want to request a feature, report a bug or ask a question?
Bug
What is the current behavior?
What is the expected behavior?
No warning. It works, so why complain?
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.
Piece of webpack config might be relevant:
Another issue on this mentioned:
Not sure if this means latest version or last entry but it is both. So that is NOT the solution.
This is especially weird because in your
loader.js
, it goes:This suggests it wants to be the FIRST entry, not the last (or latest)... But even so, why is this made into a problem in the first place? Why does this plugin need to complain about its position in the configuration??
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: