2 ms·
To be fair most framework and library examples or showcases never show the error handling or edge case pieces so I don't think it's unusual. htmx doesn't promi
by zaphar 3y ago
To be fair most framework and library examples or showcases never show the error handling or edge case pieces so I don't think it's unusual.
htmx doesn't promise to do away with client side code. Most uses of it I see still have client side code. They tend to go in one of two directions with it.
1. Web Components to encapsulate client side error handling and behavior.
2. The hx-on attribute for scripted event handling.
It's not really an anti Javascript library. It's more of a different approach to server side state synchronization.
I have to dynamic apps I use for personal usages. One is an offline first spa app so htmx won't work well for it. It's all client side code with json apis. The other has no offline use case and htmx is a great fit for it but I still have several hundred lines of vanilla javascript in there for client side behavior bits.