-
Hi all!! I'm trying to create a WASM binary from a forked version of my friend's escape2024 package so that I can use it in my js/ts project here. At first (commit here). The R-Universe build was successful (here) 💪, but I don't see the WASM binary. Logs from the "Build R-release for WebAssembly" are below.
After some (probably unhelpful) chats with Gemini I modified the project to include custom /tic.R and /tools/build_wasm.R files. The build is now failing with this error:
I'm very new to wasm and have never worked with R before. Can someone help me through the steps and which file/repo I should be pointing to in my js code once I get a successful build? Thanks a bunch in advance!! EDIT: My main brain is back to the original and appears to be building the wasm binary okay but when I try to use the binary in my js project I'm getting this.
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 6 replies
-
I think your first attempt was good. I'm not sure where Gemini got thsi but tic has nothing to do with it so remove that. To install install.packages("escape2024", repos = c("https://jgf5013.r-universe.dev", "https://repo.r-wasm.org")) You can easily test it in this WebUI: https://webr.r-wasm.org/latest/ |
Beta Was this translation helpful? Give feedback.
-
This happens when you install dependencies from
Those you can probably ignore. This happens because some of the dependencies of your package do not support WASM. But it seems the package can still be loaded. |
Beta Was this translation helpful? Give feedback.
-
Hmm perhaps repos: ['https://jgf5013.r-universe.dev', 'https://r-forge.r-universe.dev', 'https://karlines.r-universe.dev, 'https://repo.r-wasm.org'], Or alternatively you could try getting all dependencies from our cran universe instead of the official r-wasm.org repos: ['https://jgf5013.r-universe.dev', 'https://cran.r-universe.dev'], |
Beta Was this translation helpful? Give feedback.
This happens when you install dependencies from
https://cloud.r-project.org
(which does not have wasm binaries).Those you can probably ignore. This happens because some of the dependencies of your package do not support WASM. But it seems the package can still be loaded.