4 ms·
Intersting. How did you work around the issue that HTMX takes snapshots of the altered DOM (by Alpinejs) for history navigation [0]? This is the biggest issue h
by rasso 4y ago
Intersting. How did you work around the issue that HTMX takes snapshots of the altered DOM (by Alpinejs) for history navigation [0]? This is the biggest issue holding me back from using the two together.
[0] https://github.com/bigskysoftware/htmx/issues/1015 https://github.com/bigskysoftware/htmx/issues/1015
- girvo 4y agoBasically by just being careful: because these are purely rough and ready internal tools, I can be a bit picky about what gets used where, and why. For the most part I don’t have much history navigation at all, let’s me cheat :)
- naasking 4y agoWhat's the advantage of using hx-boost? Just slightly smoother transitions?
- rasso 4y agoWith `hx-boost`, you can progressively enhance your server-rendered website to an SPA, just like with hotwire/turbo [0] or swup [1] (which I'm using a lot these days). This technique can come with a few other benefits apart from nicer page transitions, like preloading links on mouseenter and caching of visited pages. [0] https://turbo.hotwired.dev/ https://turbo.hotwired.dev/ [1] https://swup.js.org/ https://swup.js.org/
- naasking 4y agoSo it's mainly used for optimizations, and it's not a critical architectural tool for building a system. I'm looking at using htmx and Alpine in a project so my takeaway is just to avoid hx-boost and rely on the built-in browser navigation.