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
module.exports = {
plugins: [
// enable a built-in plugin by name
'builtinPluginName',
// or by expanded version
{
name: 'builtinPluginName'
},
// some plugins allow/require to pass options
{
name: 'builtinPluginName',
params: {
optionName: 'optionValue'
}
}
]
}
svg-to-ts has a --svgoConfig option which looks for a JSON file. This should probably be updated to use the new module config instead.
E.g.
--svgoConfig svgo.config.js
The text was updated successfully, but these errors were encountered:
…ange
BREAKING CHANGE: svg-to-ts now ships with svgo 2. SVGO 2 has different syntax of passing
configuration. Furthermore we use the SVGO default object and dont introduce a custom fallback
anymore
#127
# [7.0.0](v6.0.2...v7.0.0) (2021-10-05)
### chore
* **(svgo) update svgo to v2:** update svgo to v2 - config object change ([688223e](688223e)), closes [#127](#127)
### BREAKING CHANGES
* **(svgo) update svgo to v2:** svg-to-ts now ships with svgo 2. SVGO 2 has different syntax of passing
configuration. Furthermore we use the SVGO default object and dont introduce a custom fallback
anymore
The svgo package is now on version 2.3.X which introduces a new way of setting the config.
Instead of a JSON file, it's now a JS module.
Docs: https://github.com/svg/svgo#configuration
E.g.
svg-to-ts has a
--svgoConfig
option which looks for a JSON file. This should probably be updated to use the new module config instead.E.g.
The text was updated successfully, but these errors were encountered: