• take() removes a class or attribute from selected elements, then adds them to the element making the call. It’s a convenient way to perform an action on everything but the given element (e.g., all other buttons in a div but this one).
  • trigger() dispatches a given event to everything matching the query. It includes options for keeping the event from bubbling if needed.
  • insert() adds HTML within or around selected items.

What’s important about q() is that you can use it entirely outside of htmx attibutes, as part of your own custom-written JavaScript functions or callbacks. You could even begin adding htmx functionality to a page by using only q() and its behaviors, hand-in-hand with JavaScript, then build outwards from that to replace a site’s legacy functionality with htmx over time.

Using htmx with Alpine.js

As a rule, front-end web frameworks shouldn’t be mixed, the better to minimize side effects and unpredictable behaviors. If you use htmx to add reactive behaviors to a page, you will get the best results if htmx (and whatever JavaScript you integrate with it) is the only source of reactive behavior.

Still, htmx makes provisions for working hand-in-hand with other ways to add reactivity. Aside from hand-written JavaScript, you can integrate the Alpine.js library.