babel-plugin-transform-typescript-metadata VS htm

MikroORM is a little better in that they have an alternative strategy that only requires your build tool to support type (1) but not type (2) https://github.com/leonardfactory/babel-plugin-transform-typescript-metadata

While I was able to achieve this fairly easily, the developer experience of manually stitching strings together wasnt great. Being myself a fan of buildless libraries, such as htm and lit-html, I figured I'd try to take a stab at implementing a DSL for component-like templating in Service Workers myself, called Service Worker Templating Language (SWTL), here's what it looks like:

after looking at your scripts file i want to convert it to jsx/htm lol

I would however highly recommend https://github.com/developit/htm

I thought the same thing, but apparently "HTM" is a JSX like javascript string template representation of HTML, and it can be found here: https://github.com/developit/htm

This seems like a case of caring way too much about something that's hardly very different. JSX versus tagged template strings can be incredibly similar to one another.

The examples in this article are using vanilla template strings to author raw html, but that only misses a couple of nicities JSX has. There are tagged template string libraries like htm[1] that do include some of the few nicities JSX has, but which are actually compatible with the official language.

[1] https://github.com/developit/htm

There is however a library that is closer to JSX (HTML-like feel) but yet does not require a build step. htm. HTM uses tagged templates to leverage template literal as native Javascript template strings. If you have not played with tagged templates, I encourage you to check this out, it's a quite powerful feature, that has recently become a part of Javascript.

You can also use preact without a build step via htm

https://github.com/developit/htm#installation

Minifying only makes sense for large dependencies, and when you download those prebundled from unpkg.com they are minified. Few are the web projects whose own code benefits enough from minifying to need it. And for those not using TS the transformations boil down to browser compatibility and JSX. Browser compatibility is someone everyone needs to check for themselves, but I would argue still supporting IE in 2022 is actively harmful. JSX is replaced by the htm library. Granted, htm is not a full replacement for JSX, but performance-wise it is fine, because modern browsers are ridiculously fast executing javascript, even on slow machines.

Our sweet little React wannabe actively publicizes itself as an alternative to React, no wonder it has perfect support for JSX as well. But if you want, you can also go the lit way.