https://htmx.org logo
Powered by
# htmx-general
  • h
    most of the time I haven't really had an issue with it
  • h
    this one specific time is alpine specific
  • h
    the reason I ask about multiple swap methods is that I don't really want to put swap method alpine on the body element but I do want the alpine component to use it
  • h
    I haven't thought too hard about this but something like running down the tree to find every sub tree w/ a swap method different than the parent, then swapping multiple times starting from the bottom up
  • m
    šŸ¤” OK, if you want to think about it a bit more and let me know what logic makes sense we can look at it. I am going to probably 7b you though, fair warning.
  • h
    yeah for sure
  • a
    Hello! I am considering using HTMX for the first time and wondering what the recommend solution is for connecting and authenticating with an API? Planning to use handlebars.js for templating but having trouble finding how to do the authentication with the API and then maintain that for the logged in user. I will be using JWT for the auth.
  • h
    How do you pass it to the backend, through a header?
  • m
    I am still working through the best architecture for my solution but any input would be helpful here, there is more content also - https://www.reddit.com/r/htmx/comments/uo8jva/alpinejs_and_htmx_architecture_help/
  • m
    I like #2 if its an option
  • m
    it should be cached after the first hit.
  • m
    But there are situations where that isn't ideal
  • m
    #2 is what Iā€™m leaning towards too, so maybe I stop overthinking and just go with it šŸ˜…
  • g
    Is the script executing multiple times?
  • g
    Looks like it from the issues you describe
  • m
    retweeted your tweet to see if anyone else has strong opionions
  • m
    in general I like to load all my JS up front and let the app run from there. As long as you aren't going crazy it should be reasonably fast and is cached after the first load (down to the compiled version by the browser).
  • m
    Of course w/ hyperscript everything is inline and compiled on demand as needed
  • m
    šŸ’…
  • h
    I'm doing #2 right now
  • h
    I am currently working on something better that I would love to link you once it's ready
  • h
    But basically in that example I just load it up in the main.ts, import everything there and then include that in the base.html
  • h
    so theoretically the way vite works
  • h
    is you will have a list of entry points
  • h
    and vite will take that list, compile it, and for each entry point have a list of required dependencies + the application code
  • h
    vite is smart about the dependencies
  • h
    so that means if all the entry points are declared, you should be able to do things like include alpine from the same source file in two components
  • m
    \> smart
  • h
    lol yeah honestly just jam it all into the header is totally fine for exactly that reason
  • m
    I think I was trying to be smart with it, keeping it simple for now and Iā€™m going to do option 2! I would be interested to see what your working on though
1...673674675...1146Latest