Ben Pate

This looks pretty cool. Since you're hooking into `htmx:configRequest`, you could probably wrap this up as an extension that could be activated/deactivated as needed. I think that's the current direction...

@Benoss -- Your second solution is the better way to go, with one small change. If you're dynamically changing the value of `hx-get`, you need to tell htmx about the...

I think this may have already been settled, but I'll just add this for posterity. Typescript is made for codebases EXACTLY like htmx. The compiler can be set to work...

Yes. Agreed. Without duplicating *a whole lot* of code, this would require that html publish a workable `swap()` method for external scripts to use. So this depends on #255

This is loosely related to the work on WebSockets, which uses OOB syntax when pushing freshly received messages into the DOM. Though it currently duplicates some of this logic, it...

@1cg - can you review this before we merge? I'm getting different results when I use `api.triggerErrorEvent()`, depending on when it's being used. For regular connection errors (like an HTTP...

Giving this a little more thought, each library has its own custom wrapper around websockets (and SSE) connections that is tailored to its own use cases. While they *do* need...

My apologies, I'm not able to run thorough tests on this. But, there should be no problem in (re-)initializing the preload extension on the `htmx:load` event because the extension uses...

For the record, during the debugging process, I played the role of an excellent "rubber duck." @bbbart bbart found and fixed the bug :) Notes to our future selves: *...

Yeah, I saw that too. But that's already in the CORS section. Not much help if you're not already searching for CORS-related problems. It wouldn't hurt to link to this...