You can just run yarn dev and open the hosted website on http://localhost:80. I checked your typo fix and the website correctly shows our repository and displays the newest desktop version (9).

But (unrelated to this change) by doing that I discovered that actually flow syntax transformation isn't set up for this package and after the flow version update which added types in this file, electron-update-server can't be run (as node doesn't understand flow syntax). Few ways to fix this:

Set up babel flow transform for this package - I don't think it's worth it, this file won't be changing much
Just use // @noflow and remove types
Use flow comments syntax. This for some reason triggers prettier for me, so I had to ignore it on the lines with types.

This revision is now accepted and ready to land.Dec 4 2023, 2:16 AM

Fix the types while we're here

While looking into the issue with Prettier here, I found this comment from somebody on the Flow team:

We will likely officially deprecate it from Flow soon.

I guess we'll have to make some changes when that happens, but this isn't the only place we use Flow's comment syntax (see D10040 and D10004), so we'll have to address that at a later point anyways.

services/electron-update-server/index.js
4	`// prettier-ignore` would have been preferable here, but it doesn't seem to work. This is unfortunate because `// eslint-disable` only works if Prettier is run from an ESLint context. That means that if some does eg. `yarn prettier --write .` from the root this file will get changed. But I guess people don't usually do that. The alternative would be either one of the other options @michal listed, or to disable Prettier for this file entirely via `.prettierignore`.
16	Using the "type annotation comments" format seems to avoid the Prettier issue