1. No js build tooling stack needed (although since vite came along, i’m less annoyed with the typical js dev pipeline)
2. The documentation site is very usable
Things i don’t know about yet:
1. How do you test htmx behaviours and components i’ve made without going full e2e (easy to make slow and brittle) - ideally I don’t really want to spin up my whole web app stack just to build out a dynamic table component
1. Can you get linting or intellisense setup? I just want some warnings in my editor for bad usage
1. How do you make sure you’re not leaving cruft behind in the DOM? Right now i’m manually checking I haven’t accidentally left dom nodes behind through my mistaken use of hx-swap
1. It’s not clear to me how to update other hx- decorated items on the page. E.g. if i need to update the id field in a link, how would i do that without resorting to a bunch of js?
1. Hyperscript looks neat but i can’t help balk at 100kb-ish dependency just to give up access to convenient js dev tooling like the chrome debugger etc.
> how would i do that without resorting to a bunch of js
I think you probably would have to. Updating a bit of the DOM directly - if you really need to do this - sounds like a job for something like alpine.js, which apparently pairs nicely with HTMX.
I'm trying to make a site that's just pure HTMX though, to see how it turns out.
I like:
Things i don’t know about yet: