It would be nice to have a babel macro that automatically runs the babel plugin to remove the runtime. That way, this project would work out of the box with "zero" config tools like create-react-app.

I'm thinking it could be something like:

import {html} from 'htm/preact/macro'

This is similar conceptually to CSS-IN-JS libraries providing a macro for their tools. See https://e

• There seems to be a bug when navigating to the catch_all route but not contributors, ex. localhost:7878/test. The current implementation panics using both rocket and actix as server.
• Rocket currently has 404 for unknown routes and this should be added to the actix example as well.

I flagged this one as a "good first issue", since it does not require any knowledge of neo.mjs itself.

Also flagged it as "help wanted", since actions & workflows are not a topic i am familiar with (well, setting up the auto npm publish one was easy).

Googled and found some input:

https://github.community/t/triggering-by-other-repository/16163

https://fabianmoronzirfas.me/tech/2019/02/

It'd be neat to have a benchmark to test our diffing needs — perf is a feature, and we should be able to catch regressions.

Given this would need to run in the browser, we'd probably need some tooling around this. I was thinking it'd be cool to run a headless Chrome instance through puppeteer, and use the [nanobench](https://github.com/mafintosh/nano