Vincent

> Is this intended? Likely not, it was probably generated with the name of the person that created the repo (namely Alex), GitHub Desktop does that for ex when selecting...

Hey, Event sources are constructed with [their own constructor](https://developer.mozilla.org/en-US/docs/Web/API/EventSource/EventSource), so no XMLHTTPRequest is made to open the connection, we can't simply plug this into htmx's request mechanism See #132, #139...

Hey, doesn't the `htmx:sseBeforeMessage` match your usecase here? It should allow you to override `event.data` which is then passed to the `swap` method https://github.com/bigskysoftware/htmx-extensions/blob/719538f486614ba48a16c7b53a4ca1f069132d97/src/sse/sse.js#L118-L123 Let me know!

Oh, indeed the properties are read-only... Maybe we should use a copy of `event` in the extension to pass down to `htmx:sseBeforeMessage`? Like `{ ... event }` ? I don't...

This would solve your immediate usecase, but I'im thinking an event-based solution would be more modular and let people handle more specific usecases as needed. With this approach, you could...

> excluding them from the NPM package That would be the best solution, maybe there's a property for that in `package.json` syntax? Haven't had time to look into this yet,...

Oh so there was such a thing as a npm ignore file, nice! Sure, feel free to do it for all extensions at once as the issue is the same...

Hello, I'm not sure to understand the issue, sorry if that's off the mark; > using the hx-trigger tag to start sse requests on a user event (like a click...

Ooh ok I get it, you want to initiate the SSE connection upon user interaction. Is there any reason not to have it initialize the SSE connection automatically on page...

Seems I somehow forgot to post a message when adding the "enhancement" label back then, but sure I don't see any reason to oppose to making the extension more flexible...