Lot of redundant wasm binaries being produced for the lite deployment

[anutosh491]

I just started noticing it this week

[anutosh491]

For xeus-cpp-lite each cell should give us a wasm module and that's all we should have.

But recently I've been seeing almost 40 odd SIDE Modules (which look like they don't have any relevance whatsoever) end up in our lite deployment (locally or through our deployment link)

No clue where these are coming from but looks like it might be Jupyterlite/Jupyterlite-xeus issue ?

cc @IsabelParedes I see the same through xeus-r-lite's link too
Do you know what changed ?

[anutosh491]

I think we might not be able to help this (and we might have to live with it) cause these are used for dynamic linking in emscripten (as we have quite some dynamic linking on our end)

This is what generates these wasm binaries.

https://github.com/emscripten-core/emscripten/blob/fe95793d1ccd1f6b54e039dc1a1234cea72b570c/src/lib/libaddfunction.js#L90

[vgvassilev]

If we can pick up the filename that’s created we can use /dev/null