Closed clehner closed 3 years ago
I think we can replace the webpack for something else, currently it is just being used to minify the generated script, but previously it was to remove an circular dependency.
Hitting on the same error on my WSL2 test on a machine with 8MB (although it might just be the VM settings). Is there a way to triage this by somehow requesting extra memory for the process?
Hitting on the same error on my WSL2 test on a machine with 8MB (although it might just be the VM settings). Is there a way to triage this by somehow requesting extra memory for the process?
Unfortunately, downgrading to WSL1 or using an actual UNIX env tends to solve these sort of headaches. I've found WSL2 to be unreliable all around. Just my two cents.
I suggest to close this issue as we now use the output of wasm-pack
directly.
I still get out of memory when building asmjs.stamp on 1c5b6af334ae59960cee37862e0e14e19dbb8443:
Can I suggest we remove it from the Makefile? I think maybe handling old browsers (which is the only reason why we would need ASM?) shouldn't be in DIDKit, but instead should be an option when compiling the frontend (which could be fully in WASM, meaning not just the DIDKit dependency).
wasm2js
completes, butwebpack
takes several minutes to run and then exits due to out of memory.