This prevents cases say where the web app is running in a terminal, but when we
try to run the desktop app it silently switches to a different and then failing
to load in a manner that is harder to debug compared to if it'd failed outright.
Ref:
- https://github.com/vercel/next.js/discussions/23932#discussioncomment-599284
Latest Node 20 (20.13.1) ships with an updated corepack which seems to insist
putting a package manager field in package.json
(https://github.com/nodejs/corepack/pull/413).
Let it have its way, hoping that this doesn't break someone's workflow
(depending on how they installed yarn without corepack or if they have a node
version that doesn't have corepack).
- Use the shared yarn monorepo configuration
- styled-components => emotion (since that's what the rest of the code uses)
- Remove Sentry (since it's gone elsewhere)
Sentry has a measurable impact on page load, a metric that I'm keen to
improve. Apparently by default it loses us 8-9 page speed points, though that
can be reduced to 3-4
(https://github.com/getsentry/sentry-javascript/issues/9179).
All of this is doable, but there are bigger tasks to deal with. This is not to
say that Sentry won't be useful again at some point, when we have time to deal
with it better. But right now, we discussed that it's just better to remove
Sentry instead of piling on to the sunk cost.
