Question about htmx 1.x Long-Term Support Timeline #3721
mikokofuyu
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Thank you for your work on htmx and for continuing to support v1.x - that is really appreciated by teams supporting legacy browsers.
I noticed in the 1.x => 2.x migration guide that you mentioned the following:
I'd like to understand what "support" entails for 1.x. Specifically, does it include maintenance of critical security issues and bug fixes for reported issues, or is it something different?
Could you also share any more concrete timeline beyond "foreseeable future"? Even a rough estimate, such as a minimum of 2-3 years, would be helpful for our long-term planning, particularly with legacy browser support in mind.
We're unable to upgrade to 2.x due to its use of the Proxy API, and we're currently debating whether to maintain 1.x long-term or write our own internal library inspired by htmx but compatible with legacy browsers. This information would really help us make an informed decision.
Beta Was this translation helpful? Give feedback.
All reactions