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
Hi, we're trying to use this plugin on Gatsby 3 and having partial success.
Some parts of the config go through, e.g. 'prefixIds' (confirmed) and a custom plugin config (confirmed), but overriding preset-default params does not work correctly.
The syntax you show in your example in the README is wrong, maybe it was targeting a dated version of svgo. Even though gatsby can compile the app, the screen shows a warning about an unknown file type on an svg path.
However, viewBox is still being removed from inline SVGs by SVGO.
If you get this and can debug the problem, that would greatly help us out as we are currently grafting a known viewBox back onto an inline svg that needs it to display correctly in a live website.
(Would also suggest updating your README and getting Gatsby's page for your plugin updated once you get the new svgo syntax in there!)
Thanks!
The text was updated successfully, but these errors were encountered:
Hi, we're trying to use this plugin on Gatsby 3 and having partial success.
Some parts of the config go through, e.g.
'prefixIds'
(confirmed) and a custom plugin config (confirmed), but overridingpreset-default
params does not work correctly.The syntax you show in your example in the README is wrong, maybe it was targeting a dated version of svgo. Even though gatsby can compile the app, the screen shows a warning about an unknown file type on an svg path.
Using the current syntax it should be more like this:
However, viewBox is still being removed from inline SVGs by SVGO.
If you get this and can debug the problem, that would greatly help us out as we are currently grafting a known viewBox back onto an inline svg that needs it to display correctly in a live website.
(Would also suggest updating your README and getting Gatsby's page for your plugin updated once you get the new svgo syntax in there!)
Thanks!
The text was updated successfully, but these errors were encountered: