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
This offers you escape hatches for when the default SVGR / SVGO config does not fit your needs.
But we'd still like to improve the Docusaurus SVGR / SVGO default configs
These configs define how you import and use SVG files in your React code, and changing those can break or fix existing sites by altering what gets rendered and how SVG components are converted to React components.
This would be a breaking change in an upcoming major version of Docusaurus (v4 for example).
We'd like to find defaults that work well for most sites and reduce the need for users to customize those configs. Optimizations should rather be safe and avoid potential SVG ids/class/whatever conflicts.
Current configs
These are the historical configs we use in Docusaurus v3:
Motivation
If you are an SVGR / SVGO expert, please help us find better defaults.
In #10677 we are creating a new
@docusaurus/plugin-svgr
plugin that you can now configure through plugin/preset options.This plugin moves this core feature to a dedicated plugin:
https://docusaurus.io/docs/markdown-features/assets#inline-svgs
This offers you escape hatches for when the default SVGR / SVGO config does not fit your needs.
But we'd still like to improve the Docusaurus SVGR / SVGO default configs
These configs define how you import and use SVG files in your React code, and changing those can break or fix existing sites by altering what gets rendered and how SVG components are converted to React components.
This would be a breaking change in an upcoming major version of Docusaurus (v4 for example).
We'd like to find defaults that work well for most sites and reduce the need for users to customize those configs. Optimizations should rather be safe and avoid potential SVG ids/class/whatever conflicts.
Current configs
These are the historical configs we use in Docusaurus v3:
Related links
The text was updated successfully, but these errors were encountered: