virtual-dom

For the most part this just works, but functions within tagged markup get weird indent assertions, e.g.,

        ${collection.map((item) => {
          const { prop1, prop2 } = workWith(item);  // eslint: expected indentation of 4 but found 10 (indent)
          return html`  // eslint: expected indentation of 4 but found 10 (indent)
            <${Widget} prop1=${prop1} prop2=${prop2} />

Is your feature request related to a problem? Please describe.
Right now ESlint isn't super helpful in catching bugs beforehand. It would be better to have a more proactive / stricter config.

Describe the solution you'd like
Example could be @strv/*'s eslint configs: https://www.npmjs.com/package/@strv/eslint-config-base

Please propose configs in this thread before PR

Starting recently, I am available and highly motivated to consistently contribute to the Neo.mjs project for the long term. However, to maximize my own & other contributors' impact, I find it necessary we overhaul the roadmap completely.

Roughly speaking, I suggest the following steps as an approach:

1. Brainstorming and gathering input (e.g. via multiple-choice surveys) from the developer

• 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.

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