Dexter Chua
Dexter Chua
Normally I would say we should first upgrade to latest emscripten with llvm backend, but llvm-backend emscripten is pretty broken for us, so I'm not sure
I'm afraid I don't have the bandwidth for that at the moment.
Depends on which part you are having trouble with.
You don't. You can set it up on localhost. You might want to have a look at how the testing setup is done at `docker/`.
I think the reason for the conflict is that I have further modified some of your changes in https://github.com/dalcde/cam-notes/commit/003ca8c2d514d821d3a1674e647ed7363d14b0ed , which your PR partially reverts.
Typescript 4.5 does not solve the problem for me. The release notes say > Finally, it’s worth noting that the only way to import ESM files from a CJS module...
I believe the offending line is https://github.com/form-data/form-data/blob/master/lib/form_data.js#L104 . When `value` is a `body` returned from `node-fetch`, the condition evaluates to `true`, because ```js body.path == undefined value.readable == true value.hasOwnProperty('httpVersion')...
Having something like Xft would be extremely helpful, but that is presumably very different from icccm and ewmh support
I suspect the morally correct thing to do would be to come up with some sort of xml description for icccm and ewmh, and generate the bindings automatically.