Sébastien Lorber

Thanks Yes we'll remove that plugin but it's technically a breaking change so it will be done for v4. The plugin is already deprecated in our docs: https://docusaurus.io/docs/next/api/plugins/@docusaurus/plugin-google-analytics

Thanks but I think it's fine in the current state, this warning is big enough  And broken links such as this one do not...

Thanks, we'd want to fix this one indeed! (for all our docs versions). PR welcome. It's weird that Google breaks links. They even discontinued their own link shortener recently. 😅

Thanks > Failing because tests run on Node 18, not Node 18.18. I asked in Discord: [discord.com/channels/398180168688074762/584803742801723424/1258853596338847825](https://discord.com/channels/398180168688074762/584803742801723424/1258853596338847825) Is this the only blocker to this PR? We still support Node 18.0,...

> `Using docusaurus start while having a index.html in the static directory will cause the following error:`` During `docusaurus start` this is normal because we don't use SSR and we...

Please try canary and [Docusaurus Faster](https://github.com/facebook/docusaurus/issues/10556), this should be fixed with the LightningCSS migration.

This plugin is quite old and difficult to maintain and reason about, with external dependencies being unmaintained forks. You can still use it in its current state, but we'll probably...

If you want to submit a PR you can. I'm not sure to understand what you have in mind and don't really plan to work on this in the immediate...

Actually the problem is more likely to be: - in v3.3.2 we had a regression, that we fixed in v3.4 (https://github.com/facebook/docusaurus/pull/10132) - our postcss setup does not yet support CSS...

Thanks for investigating. I'm not sure what is happening here, will need to study the problem to figure out.