One small note on the testing instructions is that I had to do Force Reload instead of just Reload to make it work.

Ah, in my case just reloading worked but it might depend on the state of the app. I'll update the testing instructions, thanks!

I remember that some time ago, we also introduced standalone React dev tools in Automattic/local-environment#148 - do we need both?

Oh, I overlooked this documentation when I tried to use the React Devtools. I think we can have both as they provide two different ways to access React Devtools:

• https://github.com/Automattic/local-environment/pull/148: You need to run React Devtools separately and connect it with the app.
• This PR: The React Devtools are installed as an extension to the Devtools.

Ideally, the latter could supersede the former if we find a workaround to avoid reloading the window to make the React Devtools visible. In any case, I'm ok if we rather keep one option and discard this approach 🙂.

Personally, I prefer approach in this PR to the one in: https://github.com/Automattic/local-environment/pull/148 because that one requires you to start extra things while this approach is more straightforward 👍 I also do not mind reloading the window and I think it is okay for now as long as we mention it explicitly in the documentation.

That is to say that I think we definitely should keep this approach. As for the standalone tools, we can either keep them or remove them - I do not have a strong preference. I do not use is very often and with this new approach will likely use them even less often.

Personally, I prefer approach in this PR to the one in: Automattic/local-environment#148 because that one requires you to start extra things while this approach is more straightforward 👍 I also do not mind reloading the window and I think it is okay for now as long as we mention it explicitly in the documentation.

Good point. I'll update the documentation in a separate PR to mention this.

That is to say that I think we definitely should keep this approach. As for the standalone tools, we can either keep them or remove them - I do not have a strong preference. I do not use is very often and with this new approach will likely use them even less often.

Sounds good. I also don't have a strong preference for either keeping it or removing it. Since both can live together, I'd lean toward keeping both for now.