We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
removeViewBox
Hi there! Thanks for your work on this plugin.
I discovered that the current config docs at here https://github.com/cpsoinos/nuxt-svgo#configuration are pointing out that you can do something like:
export default defineNuxtConfig({ modules: ['nuxt-svgo'], svgo: { svgoConfig: { multipass: true, removeViewBox: false, plugins: [ { name: 'preset-default', params: { overrides: { // customize default plugin options inlineStyles: { onlyMatchedOnce: false }, // or disable plugins removeDoctype: false } } } ] } } })
with svgo.svgoConfig,removeViewBox. But this setting will not work, and it will still remove the viewBox. This syntax though works for me:
svgo.svgoConfig,removeViewBox
export default defineNuxtConfig({ modules: ['nuxt-svgo'], svgo: { svgoConfig: { multipass: true, removeViewBox: false, plugins: [ { name: 'preset-default', params: { overrides: { // ... removeViewBox: false, } } } ] } } })
See here: jpkleemans/vite-svg-loader#56 (comment)
The text was updated successfully, but these errors were encountered:
docs: ✏️ correct svgo options override example
59a3f24
✅ Closes: #54
bfa9f54
Successfully merging a pull request may close this issue.
Hi there! Thanks for your work on this plugin.
I discovered that the current config docs at here https://github.com/cpsoinos/nuxt-svgo#configuration are pointing out that you can do something like:
with
svgo.svgoConfig,removeViewBox
. But this setting will not work, and it will still remove the viewBox. This syntax though works for me:See here: jpkleemans/vite-svg-loader#56 (comment)
The text was updated successfully, but these errors were encountered: