[WIP] Capture all JS dependencies in ES module imports

[JanCVanB]

TODO:

• Manually fix remaining lint errors
• Wait for Clean up various code smells #189 to merge (currently has errors that prevent full testing of this branch)
• Fully test this branch with my local Xpra server

[totaam]

The libraries should be excluded from the split, ie: mitm.html

[JanCVanB]

The libraries should be excluded from the split, ie: mitm.html

Oh, could you please explain what mitm does? And what "libraries" means in this context?

[totaam]

Oh, could you please explain what mitm does?

I don't really understand it well, it is part of StreamSaver.js - added in ce0bc83
It goes with sw.js and it should be possible to move them to /js/lib somehow but managing relative paths quickly becomes tricky so I didn't attempt it.
Many will deploy xpra to relative paths and we have to make sure things still work there.

And what "libraries" means in this context?

Anything that is going to be updated independently of xpra.

[JanCVanB]

@totaam Ah, now I understand mitm, thanks. I'll revert its modifications here, so that it remains maintainable.

The libraries should be excluded from the split

Do you mean that this PR shouldn't touch html5/lib/js/ files? If so, then this PR is impossible, since those files currently "export" their variables/functions to the global window context - they either need light (maintainable) modification to become compatible with ESM import syntax or they need to be replaced entirely by npm dependencies.

[totaam]

they either need light (maintainable) modification to become compatible with ESM import syntax or they need to be replaced entirely by npm dependencies

I would prefer the former.
Can we keep most of the formatting from their upstream source?
(to make it easier to diff with upstream)

[JanCVanB]

Closing for staleness