What is your question?

I recently updated from Javy 1.4.0 to 5.0.4 and noticed that javy build -C dynamic -C source-compression -C plugin.wasm -o my.wasm my.js places what seems to be the contents of my.js inside my.wasm, in a section called javy_source, which javy compile -d -o my.wasm my.js wouldn't do previously on version 1.4.0.

I don't really need the source code to be bundled with the wasm as I have a custom solution for keeping track of it, and it leads to my.wasm growing in size by about 50%, despite the source code compression. As I have a lot of wasm modules, the collective overhead becomes quite large.

Is there any way of omitting the javy_source "section" in the compiled wasm modules, seemingly coming from here?