Guy Bedford
Guy Bedford
I've transferred this issue into ComponentizeJS, as it's a componentize error. Ideally we'd debug the Wasm stack here to determine the source of the panic in StarlingMonkey, but without debug...
Yes exactly - it seems this is specifically for the default export function binding update. That is: ```js export function q () { } q = 5; export default function...
This might make sense as an option actually. We'd need to use a dynamic import in the instantiation body and make this a configurable option as part of the instantiation...
It sounds like you want some kind of partial instantiation here? It's an interesting use case, perhaps there's a way to define it with CLI arguments so that the given...
This should ideally be implemented along with the ESM instance imports and should likely also go with unflagging `--experimental-wasm-modules`.
This landed in #56919.
This out of memory error may be fixed in https://github.com/bytecodealliance/ComponentizeJS/pull/184. I'm running a new release cycle right now, do try it out on the latest versions when you can.
For the repeated calls error, that sounds like https://github.com/bytecodealliance/ComponentizeJS/issues/80.
For AOT, the fix for this is to set the environment variable `RUST_MIN_STACK` to a larger value. We should include this in our Weval execution by default (@vados-cosmonic would be...
This works well by default - `RUST_MIN_STACK: Math.max(8 * 1024 * 1024, Math.floor(freemem() * 0.1))`