Is it possible to encapsulate Hot Behavior as a reusable function?

[ryansolid]

I thought I had found a way that worked but I realize now there are some weird compilation side effects.

When I've created HMR solutions in the past I've generally passed the module.hot to a separate reusable handler. It makes it a lot cleaner since the process I use for HMR is create a HOC that uses the accepted module to set a signal and recreate the wrapped component.

Ideally I was trying to make this work:

export default _$hot(MyCompnent, import.meta.hot)

where _$hot is my wrapper. But this doesn't seem to pass through properly. I tried to directly pass accept but it causes a weird bug if there are any strings after it:

export default _$hot(MyCompnent, import.meta.hot.accept);
_$delegateEvents(["click"])

I noticed "click" was getting rewritten to "/src/component/click" which I'm gathering is because the dependency version of hot where you name the dependencies needs the full path but users don't write that so the transformation looks ahead for strings to transform. Sure I could do something with the compiled output but this all points to me likely doing something unintended.

Am I right in assuming that unlike some of the older methods (Ie.. module.hot) this one isn't expected to be able to be passed outside of the module and I should try to come up with a different solution?

[ryansolid]

Nvm.. I found a new solution.. where I use a factory to create the HOC, and the accept handler.. and keep the hot code in the component. Definitely less clean but probably more expected.