Error: Cannot find module '@node-rs/argon2-wasm32-wasi' when deploying to fly.io
Hello team Wasp!
Suddenly I'm getting an
Error: Cannot find module '@node-rs/argon2-wasm32-wasi' error when deploying my app to Fly.io.
The app was already deployed and functional before this deploy, and I have changed nothing to the backend, so I'm not sure where this error is coming from?18 Replies
Hi @WWWillems. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Hmm, I don't know enough to give you a confident answer yet. The knowledge sources provided do not contain information about the specific error
Cannot find module '@node-rs/argon2-wasm32-wasi' when deploying to Fly.io.
However, it's worth noting that deployment issues can sometimes be related to the version of Wasp you're using or the structure of your project files. Make sure you're using the latest version of Wasp and that your project files are correctly structured.
You can check your Wasp version by running wasp version in your terminal. If you need to upgrade, you can do so by running curl -sSL <https://get.wasp-lang.dev/installer.sh> | sh -s -- -v 0.12.4 (replace 0.12.4 with the latest version number).
For more information on deploying your Wasp app to Fly.io, you can refer to the official Wasp documentation (https://wasp-lang.dev/docs/advanced/deployment/manually#deploy-to-a-flyio-app).
If the issue persists, I recommend reaching out to the Wasp community on Discord or opening an issue on the Wasp GitHub page for more specific assistance.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @WWWillems, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?I am using Wasp version 0.14.0 btw
And the local dev build works without throwing any errors.
If I try to add the
@node-rs/argon2-wasm32-wasi package manually, I'm getting an error @node-rs/[email protected]: The CPU architecture "x64" is incompatible with this module. as I'm using Mac OSX M3.Hey @WWWillems always nice to hear from you :)!
I see we had similar error reported recently here https://github.com/wasp-lang/open-saas/issues/248 . We are using Oslo library and I see they had this issue -> might be connected with them, please check their GH issue on it (link is in GH issue I shared).
@miho will be the fastest to figure this out but he is out will be coming back on Monday!
Thanks, already stumbled on that thread. Quickly tried suggested fixes but ran out of time. Will try again tomorrow. Did a manual rollback for now. Hope we can resolve it quickly as i can’t deploy updates to my live app now 😢.
btw @WWWillems what are you building? Would love to see it in action if you can share 😄
I’m building a SaaS app for teams to manage their AI prompts. Will share it soon! 😉
@WWWillems which version of Wasp are you using?
Oh cool! @matija had a similar idea ^^
0.14.0
Could you maybe share your app in a Github repo so I can test it out? 😄 my Github username is
infomihosent you an invite on github
dont forget to run dev seed when setting up 😉
not sure if you need to actually run the project, but there's quite some
.env vars to run it as wellI'll attempt to deploy to see what happens first 😄 I'll ping you probably tomorrow since I won't be able to play around with it until later today
Sure np, thanks in advance for the effort!
Any luck?
Have you tried deleting the
yarn.lock and package-lock.json and running wasp clean and then wasp start locally? And then deploying?
Cool logo btw 🙂Hmz not yet, will try in a bit.
Thanks! Still validating the idea so both code & graphics arent ready yet though.
lol ok that seemed to fix the issue 😬 sorry for not thinking about this earlier 🤦🏽♂️
thanks!
I suspect the yarn file was the culprit. Did you run yarn install or smth like that in the project? 😊
yes probably, I'm developing a lot of projects in parallel, some use npm, some use yarn so I must've made a mistake. 😓
Okay good to know. I'm glad it worked out for you!