-
-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
svg-spritemap-webpack-plugin since SVGO v2.4.0 release #175
Comments
Thanks for the heads-up. This is an interesting change, to say the least... They overhauled the entire defaults setup and deprecated the old one while the new one is not compatible at all so now this plugin has to support both systems. The changes in 500280a should handle this, all tests are passing with both SVGO 2.3.0 and 2.4.0. Are you able to verify this on your end as well? |
Hey @cascornelissen, thank you for the commit, I'll try to test that tomorrow. |
@jimblue (or anyone else running into this problem), had any time to verify it already? |
Have the same issue |
Was getting the same warning as OP so I tested it with 500280a and while the issue is fixed - no warnings are logged - the output spritemap changed unfortunately. |
@meelkor, thanks for testing 500280a out and reporting your findings. Can you share your configuration so that I can check what's happening? An update to SVGO can always change the output of the spritemap and it's not entirely clear to me whether the problem you're describing is about having a different output or the As you've probably figured out we can't exclude the default-preset plugin from this project as there's overwrites that need to be made in certain scenarios. If anyone has the same issue, please try out the current
|
hello below is the config, the sprite is working fine but the "preset-default" warning remains.
|
@zavod008 are you talking about the |
@cascornelissen 1) yes "extendDefaultPlugins" utility is deprecated. 2) from npm. ok i try install master version |
@cascornelissen |
Description
This plugin stopped working in project using latest SVGO release 2.4.0
Expected behavior
This should work with latest SVGO update as SVGO is a peer dependency of many projects.
Actual behavior
When running webpack :
System information
The text was updated successfully, but these errors were encountered: