Update & fix react messaging

[FredKSchott]

For the Pika CDN, we now actively maintain ESM versions of React & React-DOM. So now we can start pointing to those in our docs instead of @sdegutis's (which were great, but no longer appear to be maintained).

While doing that, I discovered that in many cases these custom messages weren't being displayed. I fixed that, and added some tests.

[yukukotani]

Nice! Just to make sure, would @pika/react be open source?
Closed source may cause the anxiety about being abandoned.

[FredKSchott]

Of course, that's a good point. I'll open source the repo I'm using to build it tomorrow, which is really just a wrapper around https://www.npmjs.com/package/react-ecmascript

[drwpow]

Interesting! I myself have taken a crack at building ESM versions of React. It’s not impossible, but it is a bit of work based on their pipeline.

It’d be nice of react-ecmascript if it kept up with React versions (that repo seems 13 months old?).

Maybe with my spare time in the next few weeks I could look into helping that project fill out the missing React versions.

[FredKSchott]

Yea, it's a bit of a pain but https://www.npmjs.com/package/react-ecmascript takes care of the worst of it.

The nice thing is that you can tell it which version to build, so even though the repo is old my script uses it to build the latest React v16.12.0.

Here's the repo! https://github.com/pikapkg/react

The only thing that I'd like to add is a GitHub Action that runs nightly, checks for the latest React release, and rebuilds/publishes to npm automatically. I have an automatic job that I can run on my computer, but it still requires human intervention for me to publish the package itself.