Trying to deploy, getting a "(reading 'extraneous')"error.
For context, I did migrate from various versions of wasp 0.16.x to 0.17.x, and I think that might have something to do with the problem.
10 Replies
Hi @tacticaltuna4016. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I'm sorry, but the knowledge sources provided do not contain any information about a "(reading 'extraneous')" error during deployment, nor do they cover migrations specifically from Wasp 0.16.x to 0.17.x. The sources discuss issues with migrations between other versions (such as 0.11.x to 0.12.x), deployment errors, and some common troubleshooting steps, but there is no mention of this specific error or the migration path you described.
If you can provide more details about the error message or the context in which it appears, I may be able to help further. Otherwise, I recommend checking the official Wasp documentation for your migration path or reaching out to the Wasp community for support.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @tacticaltuna4016, 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?
Alright, I'll wait for human support - thank you.
Hi, which deploy command are you trying?
I'm trying to deploy my app to fly.io using "wasp deploy fly launch chatter-real mia"
Can you try regenerating your package-lock? Remove the file and run
lw build againremoving the package-lock and rebuilding it does not seem to fix the problem
Should I provide anything to help assess the problem?
are you using a custom Dockerfile?
no, i do not believe so. Is there anyway to check? I apologize - I'm a very amateur programmer.
Wohooo @tacticaltuna4016, you just became a Waspeteer level 1!
Hey @tacticaltuna4016, sorry for being slow, Wasp team is currently on retreat, so we've forgot to re-check this problem.
To confirm you did try to
wasp clean in combination with removing a package-lock.json?
Could you:
1) list all of the steps that you do
2) say the exact version you use (wasp version)
3) paste the current deps you have (wasp deps)
4) paste the Dockerfile from the .wasp/build folder? (you have to use wasp build first to generate it)