Vincent

Hey! Feel free to open documentation PRs (we require opening issues for new features but doc is ok), especially if the currently documented example doesn't work 😅

@alexpetros the always burning topic! As for your proposal, the issue with the `interactive` state is that, if I recall correctly, it was causing some issues with module imports (see...

I think the issue with the initial readystate check (i.e. `!== 'loading'` vs `=== 'complete'`, as the latest PR above reverts the ready state check to what it was initially)...

Yeah there have been multiple PRs and issues about this topic over time: PRs: - #1485 - #1659 - #1672 - #1681 - #1688 - #1972 - #2037 - #2040...

Hey @andrew-ebsco , appreciate that you're taking time to look into this. I must admit I'm a bit confused by how we did a full cycle on this topic again....

Hey, it seems (I know nothing about all this so you tell me 😆) we have esm support in [v2 alpha](https://github.com/bigskysoftware/htmx/blob/v2.0v2.0/dist/htmx.esm.js), if you're willing to take a look and test...

Hey, we are moving extensions to a separate repo and website (on a subdomain) for htmx 2, so this whole section will be reworked! I would suggest holding off such...

Hey @rekado, PRs are a bit stalled at the moment as we're focused on htmx 2, we'll get to PRs (and issues) again once htmx 2 is out. Please note...

Hey, are you still interested in that change @rekado ? If so, please retarget to `v1` as explained above, and/or make another PR to the [extensions repo](https://github.com/bigskysoftware/htmx-extensions), thanks!

What is the difference / added value compared to the already existing [`find` keyword](https://github.com/bigskysoftware/htmx/blob/master/src/htmx.js#L619)?