undefined | Better HN

0 pointsrecursivedoubts2y ago0 comments

No major changes, it should be about 99% API compatible with htmx 1.x. Big things:

- Websocket & SSE support will be completely pulled out to extensions (already available in 1.0)

- We will drop IE support

- We may include a "morph" swap strategy based on idiomorph (https://github.com/bigskysoftware/idiomorph/)

- We will change a few defaults around how HTML is parsed, taking advantage of the removal of IE support

Hopefully transparent to the vast majority of htmx users.

0 comments

bardak2y ago

Will HTMX 2.0 have a smaller bundle size since you are removing things? I don't think HTMX is too big or anything but I have a love tiny libraries.

And on that note do you think that a smaller striped down version of HTMX is feasible like petite-vue is for vue

recursivedoubtsOP2y ago

I don't think the bundle size will shrink too much, especially if we include the morph-style merge, which is somewhat complicated

yes, I think you could do a stripped down htmx that doesn't support a lot of the stuff htmx does, particularly life cycle events and more elaborate swapping mechanism

for example, most response headers could be just done as the HX-Trigger response header + some client side scripting

history support and form-value gathering is likewise a source of complexity and code that could be omitted or done less completely

bardak2y ago

Sounds like reasonable places to strip out stuff while keeping the fundamental features. I think the history support would be important enough to keep though.

j / k navigate · click thread line to collapse

0 pointsrecursivedoubts2y ago0 comments

No major changes, it should be about 99% API compatible with htmx 1.x. Big things:

- Websocket & SSE support will be completely pulled out to extensions (already available in 1.0)

- We will drop IE support

- We may include a "morph" swap strategy based on idiomorph (https://github.com/bigskysoftware/idiomorph/)

- We will change a few defaults around how HTML is parsed, taking advantage of the removal of IE support

Hopefully transparent to the vast majority of htmx users.

0 comments

bardak2y ago

Will HTMX 2.0 have a smaller bundle size since you are removing things? I don't think HTMX is too big or anything but I have a love tiny libraries.

And on that note do you think that a smaller striped down version of HTMX is feasible like petite-vue is for vue

recursivedoubtsOP2y ago

I don't think the bundle size will shrink too much, especially if we include the morph-style merge, which is somewhat complicated

yes, I think you could do a stripped down htmx that doesn't support a lot of the stuff htmx does, particularly life cycle events and more elaborate swapping mechanism

for example, most response headers could be just done as the HX-Trigger response header + some client side scripting

history support and form-value gathering is likewise a source of complexity and code that could be omitted or done less completely

bardak2y ago

Sounds like reasonable places to strip out stuff while keeping the fundamental features. I think the history support would be important enough to keep though.

j / k navigate · click thread line to collapse