Brian
Brian
I have a solution to this problem that I'm working on. The proof of concept is done. The basic idea is that I use enums with tuple varients to define...
I think this could be an issue with the webpack plugin. I'm currently running my own project, not related to WebGL but I'm building using @wasm-tool/wasm-pack-plugin. When I try to...
Try building in release and see if the issue persists. In a project that I was working on, I found that the debug build included type information that was larger...
I had this issue myself recently. Hoping to see this get merged so I can use Lapce in my WSL environment.
Keep up the good work! Looking forward to seeing the new release.
You're welcome! Thanks for all the hard work on this great project!
Hi Ryan, thanks for the idea. I ran the command that you mentioned, but nothing was output to the console at all. I assume that means that the checks were...
For additional context, I only run into errors when using cargo-component. If I compile to windows-msvc or directly to wasm32-wasi, I don't see any errors. For more context, I found...
[wasm-chumsky-type-info.txt](https://github.com/bytecodealliance/cargo-component/files/15094900/wasm-chumsky-type-info.txt) I dug into the `.wasm` file and found that the type information generated for the Chumsky parser is massive -- 19.3 megabytes on its own (see attached file), well...
Thanks for the suggestions. I tried using `wasm-tools strip` and it did significantly reduce the file size, but when I ran `wasm-tools component new` I received the same error message...