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
Is your feature request related to a problem? Please describe.
Parcel's caching is most effective when config files are JSON files. The effective (=exported) value of JS config can change arbitrarily meaning that JS config files always have to be treated as "modified" and svgo has to be rerun for every file (even though the user didn't change anything).
For the first config example in the readme, a JSON file would suffice (so a svgo.config.json):
Is your feature request related to a problem? Please describe.
Parcel's caching is most effective when config files are JSON files. The effective (=exported) value of JS config can change arbitrarily meaning that JS config files always have to be treated as "modified" and svgo has to be rerun for every file (even though the user didn't change anything).
For the first config example in the readme, a JSON file would suffice (so a
svgo.config.json
):Describe the solution you'd like
But for disabling a single plugin, either
extendDefaultPlugins
need to be used, or all plugins need to be listed.What's missing is a way to achieve what
extendDefaultPlugins
does but without needing a JS config file. So for example something along the lines of:Additional context
Trying to avoid having to invent our own svgo config file format for Parcel...
The text was updated successfully, but these errors were encountered: