Html Entities inside inline SVG do not render correctly

[blemelin]

🐛 Bug Report

Prerequisites

• I'm using the latest version of Docusaurus.
• I have tried the npm run clear or yarn clear command.
• I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
• I have tried creating a repro with https://new.docusaurus.io
• I have read the console error message carefully (if applicable)

Description

Html entities inside inline svg does not render correctly. They seems to be escaped twice.

Have you read the Contributing Guidelines on issues?

Yes

Steps to reproduce

Here are the steps to reproduce the issue.

1. Create a SVG with special characters like < or >.
2. Add it to any doc by inlining it (see this)

Expected behavior

Actual behavior

For your information, I can use the <img> tag and it works just fine, but I need the text to be selectable (yeah...that's a weird requirement...I know....).

Your environment

• Windows 10 Build 19042.1083
• Firefox 89.2.2
• NodeJs 7.3.0

Reproducible demo

Live Demo : [Deleted]
Repo : [Deleted]
intro.md file : [Deleted]

[lex111]

Fix for this bug here -> gregberge/svgr#553, so we will wait for merge that.

[Josh-Cena]

Should be fixed

[lex111]

Actually, this is not fixed. However, a new major version (in alpha stage) of svgr/webpack has been released which fixes this issue. Therefore, @blemelin you can upgrade your local dependency "@svgr/webpack" to "v6.0.0-alpha.0" to resolve the bug. We on our part, will wait for more stable version.

[Josh-Cena]

In that case let's reopen & wait for the version bump on our side🤷‍♂️

[lex111]

Resolved in #5958.

However since @svgr/webpack dependency is explicitly listed in the package.json when initializing of Docusaurus site, this library must be manually updated to "^6.0.0".

[Josh-Cena]

However since @svgr/webpack dependency is explicitly listed in the package.json when initializing of Docusaurus site, this library must be manually updated to "^6.0.0".

I guess it's actually fine, because in our core we prioritize node_modules of the core itself to the site's node_modules so that the deps is always the version required by the core