Sébastien Lorber

Thanks for taking a look Docusaurus isn't using React 19 yet so I'll have to make a POC of upgrade to see if I can reproduce. I'll investigate more at...

Yes it looks very similar to this other bug fixed by @sophiebits in https://github.com/facebook/react/pull/26228 However in our case it doesn't seem to be fixed under v18.3.0 Similarly, I can confirm...

I can also confirm the bug is not there anymore with `19.0.0-rc.0`

I'm not sure the React team is planning any new v18.x release anymore considering v19 is around the corner. v18.3 was released only to add extra warnings to help us...

@tats-u I'm not a Meta employee and not part of the React core team. I have no weight on their decision to release another v18.x. Considering v18.3 was released 2...

v3.6 is out: https://docusaurus.io/blog/releases/3.6 PR ready to review I kept the former `^3.5.0` range you used, I don't think it's necessary to require a newer version of Docusaurus. --- Note...

Just realized I'm upgrading the Babel website to use SWC 😅 hope you are fine with this

PR ready to review @nicolo-ribaudo, v3.6 is out: https://docusaurus.io/blog/releases/3.6

Thanks 🥳  Wasn't that long before but still cool to see the overall build time reducing

Thanks @SethFalco , I'll study all that and probably take your suggestions for the upcoming major version of Docusaurus. Maybe SVGO v4 will also be released at that time.