Sébastien Lorber

Just a random comment: for Docusaurus we moved from pMap to worker thread pool and saw a SSG improvement of ~50%. Maybe not as critical for React Router, but worth...

I'm exploring how we could fix those issues in https://github.com/facebook/docusaurus/pull/11228 The problem is that the fix is likely to be a breaking change, and we need to figure out how...

Docusaurus v3.9 will throw a clear error when it encounters i18n translation key conflicts: https://github.com/facebook/docusaurus/pull/11228 And you can resolve those conflicts by adding a unique `key` attribute to sidebar items...

In v3.9, unlocalized sites shouldn't need to worry about translation key conflicts anymore: https://github.com/facebook/docusaurus/pull/11304

For Docusaurus v3.9.2 we are also fixing/completing the support with the `sidebar_key` front matter: https://github.com/facebook/docusaurus/pull/11490 If you have `Feature1/API/index.md`, you can pass a unique key such as `feature1.api` instead of...

Note: I reverted the Docusaurus v3.4 change to unbreak search plugins in v3.5. Although you should still apply a fix on your side. See reasons here: - https://github.com/facebook/docusaurus/pull/10311 - https://github.com/gabrielcsapo/docusaurus-plugin-search-local/issues/82...

Docusaurus v3.5.2 has been released and should work fine with this plugin (I tried with v1.2) --- Note: you may get another error while building your site. ```text [ERROR] Error:...

Yes, that would also work but you'd have to also change deps to ensure all RC users upgrade to v1.0 stable v1.0 stable only works for Node 18.17+ and Docusaurus...

Thanks! I think a separate table makes more sense. I guess something like this could be nice, with the ability to count the number of files and the change too....

Agree we should probably do that. I've seen React and Next.js bumping to the next minor version instead, it's probably better than a patch.