Emotion changed to use exports map, and esbuild wasn't pivking the right entry anymore,
resulting in react not being detected, and thus not bundled, and thus missing at runtime!

I changed the tsup/esbuild config to prefer the ESM version, and this seems to have fixed the issue.

Many thanks to @anderist for the assist!

…the suggested fix by @anderist

He suggested that 'hiding' the dependency on an export that may or may not exists away from bundlers would solve it.
This is what they do in emotion itself, but esbuild optimizes that away again.

# Conflicts:
#	code/yarn.lock