"fixi" seems to be a stripped-down version with just the essentials. I'll be asking the AI whether upgrading to 4.0 or fixi makes more sense for my project.
"fixi" seems to be a stripped-down version with just the essentials. I'll be asking the AI whether upgrading to 4.0 or fixi makes more sense for my project.
The idea of htmx 4 started to germinate when I decided to create fixi and, in doing so, got more familiar with the fetch() API and async programming in JavaScript. (htmx had always used XMLHttpRequest due to backwards compatibility issues.)
[...]
Development has been very smooth. We started a port of fixi + the htmx test suite. Over time, we rediscovered why htmx did many of the things that it did and moved our new implementation closer and closer to the old one. At this point the behavioral differences between 2.x and 4.x are relatively small and where they do diverge we have made explicit choices that we feel will put htmx-based applications in a good spot for being 100-year web services
[...]
As mentioned above, htmx 4, from a user’s viewpoint, is almost identical to htmx 2. There are three major changes:
Attribute inheritance is now explicit by default rather than implicit by default (this is the biggest upgrade item)
The htmx event names have been standardized & cleaned up. Some advanced users may need to change the events they listen for.
History support now does not use localStorage by default (which was a cause of many support headaches). Most people won’t notice this at all.
"fixi" seems to be a stripped-down version with just the essentials. I'll be asking the AI whether upgrading to 4.0 or fixi makes more sense for my project.
From the article:
[...]
[...]