Mariss Tubelis

@tacman @andryyy @1klap @donseba @edgmic good news - I implemented the possibility to import HTMX extensions as ESM modules in [this PR](https://github.com/bigskysoftware/htmx-extensions/pull/123). Please check it out. If it gets merged,...

@believelody thank you - this is a very relevant question. All extensions can be installed using npm. The package naming is `htmx-ext-extension-name` (replace `extension-name` with the name of the extension),...

@ChrisJefferson and @glossd, I have created a PR significantly elaborating the instructions of setting up HTMX extensions. Based on your inputs, I have made the importance of enabling the extensions...

@tomdtp, @Telroshan, @sameer-dudeja I have created a PR updating the documentation of extensions and including guidelines for npm/bundler installation. This should solve the issue. https://github.com/bigskysoftware/htmx/pull/3078

@guacs this issue is fixed in https://github.com/bigskysoftware/htmx-extensions/pull/106, please check it out. I have tested it with your example and the loading indicator does not show up anymore.

@Telroshan I believe that this PR should be closed without merging. @bogdano HTMX request headers should not be added by the preload extension. This logic should stay with the core...

@ALameLlama Thank you! I have addressed all your comments in https://github.com/bigskysoftware/htmx-extensions/pull/106.

I have fixed this issue in https://github.com/bigskysoftware/htmx-extensions/pull/106, since I was receiving two comments about it there. I have used @meln1k solution as a foundation and implemented @Telroshan idea to reuse...

@Telroshan please don't review it yet. I converted to draft. Unfortunately I realised it won't be as easy as this. When integrating an extension with `import` statement, we need to...

@Telroshan Okay. It's all ready for review now. Do you know who are the most relevant reviewers for this type of change?