Dependency issue with fly.io server deploy
Hello everyone 👋 ,
I followed the instruction and deployed SaaS template with
client and database were created with no issues but server returns attached error message. 👉 In short fly server machine logs these missing dependencies -
wasp deploy fly launch <project-name> iadclient and database were created with no issues but server returns attached error message. 👉 In short fly server machine logs these missing dependencies -
Error: Cannot find module '@node-rs/argon2-wasm32-wasi'
- Error: Cannot find module '@node-rs/argon2-linux-x64-musl'
👉 I narrowed it down to being caused by: https://github.com/pilcrowOnPaper/oslo/issues/25 caused by oslo and lucia dependency @node-rs/argon2 which is used by wasp I am not sure how to configure the sdk versions as it seems to be built in wasp cli commad.
👉 It seems to be linked to this recently opened wasp issue: https://github.com/wasp-lang/wasp/issues/2136
Wasp: 0.13.2
🤔 I wonder if I am the only one with this dependency error...8 Replies
Hi @otrojka. 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 issue you're encountering with the
oslo and lucia dependencies during the server deployment on fly.io.
However, I can tell you that Wasp does have a system for managing dependencies. In the new structure of a Wasp project, dependencies are split into 4 groups: Project and user dependencies, SDK dependencies, Server dependencies, and Client dependencies. These are listed in various package.json files throughout the project structure (source (https://github.com/wasp-lang/wasp/issues/1595)).
If the issue is related to the versions of oslo and lucia being used, you might need to check these package.json files to see if you can adjust the versions there.
For more detailed help, I would recommend checking the Wasp documentation (https://wasp-lang.dev/docs) or reaching out to the Wasp community on their Discord server (https://discord.com/invite/rzdnErX).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @otrojka, 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?@kapa.ai I have rephrased my question
Let me check the knowledge base for you. One moment! :books:
----------------------
I'm sorry, but I can't assist with that.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @otrojka, 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?
This is very strange! Could you retry deploying (delete the Fly apps, delete the TOML files).
Those are native deps for password hashing ... But nobody so far had this issue. Maybe it's a transient Fly issue, those happen from time to time.
Fly was having a bit of a hiccup at this point in time, I think this is likely issue on the Fly side
Hey @otrojka, I'm having the same issue when deploying to Railway. Did you find a way to fix this error?
Yes, but I call it a workaround. I have created a new blank wasp project and deployed it using the wasp cli. It worked so I have migrated my source code into newly generated project. And error disappeared 🙂
Could you maybe share more details? Are you using Open SaaS? How did you try deploying it i.e. which commands did you run?