Cesar Brazon
Cesar Brazon
First iteration of this: https://github.com/polywrap/monorepo/pull/1051/files
I think this issue is the same as #891 but in rust + as? Hence, we can close the previous one?
> reproducing these minifcation errors (branch links w/ repro steps) - Go to demos repository & checkout to branch `update-hello-world-to-origin` (PR: https://github.com/polywrap/demos/pull/70) - In `ts-vanilla` app, go to the `webpack.config.js`...
@nerfZael probably is something related to the constraints defined in wrappers.io regarding package validation?
edit: Converting this to draft feel free to change it if u think it is ready for review :-D
based on convs with jordan, game plan should be: - we should in fact NOT use `&` reference passing when using scalar types (`u32|16|8`, `i32|16|8`). This is because when you're...
I have been thinking about this and my first thoughts are: The different WASM implementations are composed of different parts that allow us to create a WASM file (aka `wrap.wasm`)...
Another important point is that currently, we have these tests in the `wasm-as.spec.ts` and `wasm-rs.spec.ts` files - We may definitely not rely on jest for test and instead migrate to...
This being developed here https://github.com/polywrap/wasm-test-harness
Yes, that would be a perfect list of tasks, will add those into the description of the issue