Well it took some effort, but new executables are published!
Give those a shot and see how it goes.
I cleaned up some logging in general, so there is an updated Docker container as well, but that’s really an optional update - no urgent need to change if yours is still running smoothly.
As always, special thanks for @jkp, @TN_Oldman and others for graciously helping so many people in this thread with questions - it’s definitely noticed and appreciated. With my limited time, it’s about all I can do just to keep the core code running, so I never have as much time as I’d like to help with those. Still, I know Docker can be overwhelming, so hopefully one day I can get some better docs put together on that.
The technical solution ended up going something like this:
- Fork hjdhjd’s myq library and set the tsconfig back to output commonJS
- Revert other dependences to use earlier commonJS versions
- Run a new build with the above changes
- Publish to my own npm package
- Update the bridge server code to pull from that package instead of the original one
- Celebrate the fact that pkg successfully handles those and spits out the exe’s again
While I’m thrilled that worked, this setup feels somewhat tenuous. If we get to the point where the library needs further changes, it could get dicey if I ever have to deal with something that is ESM-only or that the packaging process just doesn’t like. I will feel a lot better whenever the packaging process handles ESM. The good news is lots of people are motivated to make that happen, so we’ll see how it goes.