Jason Miller

It's identical to JSX, since the output is just calls to the `createElement()` / `h()` function for whatever framework you're using. In the case of Preact, those rules are roughly:...

This is something we gave up when moving from using the browser's HTML parser to a custom parser in 2.0. The tradeoffs of being able to run directly in Node.js...

I understand that for some use-cases, the library size is less important. However, there are potential performance reasons to use htm without transpiling in production - including some interesting tradeoffs...

Just an addendum: I think it would be both possible and reasonable to add extended parser error messages to `babel-plugin-htm`, since it doesn't get loaded at runtime.

Hi @LionsAd! Sorry for the slow response - it'll be a few days before I can merge this. I have to add a test case for it based on your...

Interesting! If it's not a huge undertaking I think that might be nice. The idea of it baking in the JSX pragma based on the path (like you've shown here)...

Hi @klvenky - sorry for missing your question. Nobody has taken it yet, though I'm afraid I actually don't know where to start! I've never written or used a "babel...

@broofa `htm` version 1. I believe the readme mentions this: https://github.com/developit/htm#improvements-over-jsx

This is not addressable, since the behaviour described would be specific to a given attribute. For example, htm explicitly cannot treat falsy (combined or otherwise) values within some attributes as...

@julien-f I will be releasing a reasonably decent solution for this issue soon. Crawls a babel preset tree and serializes it to relative filepaths, which you can then mutate as...