meta: add react dev dashboard

[mifi]

This reverts commit ff416f9.

(cherry picked from commit 44ead928f0c5c82563d29013a46e59c9397c9f8b)

#5260

[github-actions]

Diff output files

No diff

[Murderlon]

Tested locally and I get add the hooks as our setup breaks. This has to do with how we setup vite for the rest of our dev setup. Since we already have examples/react-example, which we can perfectly use for local React development as we just reference the workspace packages, I think we can close this.

[mifi]

I get add the hooks as our setup breaks

what do you mean by that?

We had so many problems with broken uppy in react in the past and misunderstandings around how it works, so I think it makes a lot of sense to have a react dev dashboard with hot reload where we can easily test our code in react too before committing.

examples/react-example, which we can perfectly use for local React development

I strongly disagree:

• I usually test with yarn dev:with-companion, not using projects from the examples folder. Having react also in yarn dev will help reduce the chance of introducing react bugs. Without this PR I'd have to run two yarn dev command in different folders to test everything.
• When using cd examples/react-example && yarn dev:
  • companion is not active so the companion part of uppy cannot be tested.
  • there is no hot reload, so you have to stop/start the yarn dev command as well as rebuild uppy every time you make changes
  • you don't get the convenience of just changing .env variables in order to enable different options/plugins
  • if you start both commands, depending on which of the two commands you started first (yarn dev:with-companion or cd examples/react-example && yarn dev), you'll get one running on port 5173, and the other on 5174. if you start the other way around, you'll get the opposite result. this is first of all confusing, and it causes local storage & cookies to be lost, and it completely break because of CORS when testing companion (origin 'http://localhost:5173' has been blocked by CORS policy)