Jérémy Lal

It only outputs what you tell it (a web page, or directly html) to print. Some javascript can also be injected, so you can do anything you need on top...

My opinion is that WebSocket should be in core as well, and that uws has been a game changer for many developers because it brought high performance: think about serving...

@kasicka you should have a look at how debian is dealing with it. node-undici package is building the wasm files from source, there, and nodejs package embeds the result.

@mhdawson currently the [nodejs debian package replaces deps/undici/undici.js](https://salsa.debian.org/js-team/nodejs/-/blob/master/debian/rules#L245) during build by [the one built by the node-undici debian package](https://salsa.debian.org/js-team/node-undici/-/blob/master/debian/node-undici.install) using a [slightly patched](https://salsa.debian.org/js-team/node-undici/-/blob/master/debian/patches/fix-wasm-build.patch) version of undici's build/wasm.js. However, that's suboptimal...

@GeoffreyBooth there two use cases (that ideally are selected by ./configure flags, or worse, by local patches): 1. Node authors distribute a binary bundling many other libraries as much as...

I second @khardix : it's "open-source distribution" as in: everything is *built* from open source code.

Perfect !

[log for riscv64](https://buildd.debian.org/status/fetch.php?pkg=nodejs&arch=riscv64&ver=18.6.0%2Bdfsg-4&stamp=1659442361&raw=0)

BuildImage = (BaseImage + BuildOverlay) so the build script runs on BuildImage to fill DEST_DIR which is then installed into FinalImage = (BaseImage + FinalOverlay) ? The BuildOverlay, in this...

Maybe a solution is to use systemd-nspawn `--overlay` switch in `run_build_script()`, mirroring `mount_overlay` behavior ?