Cannot find module 'wasp/client/operations' or its corresponding type declarations.
I was coding when seemigly, all of my wasp imports just stopped working, and they now say:
Cannot find module 'wasp/client/operations' or its corresponding type declarations
Cannot find module 'wasp/client/operations' or its corresponding type declarations.
Not really sure what I messed up here
7 Replies
Hi @ArjunSohur. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
This error usually occurs when the Wasp compiler hasn't run or something broke in the
.wasp
folder. Here are a few steps you can take to resolve this issue:
1. Check the Wasp version you have installed by running wasp version
in your terminal.
2. Try running the Wasp compiler by executing wasp start
in your terminal. This command needs to compile the SDK for you to have all the wasp/*
packages.
3. If the above steps don't work, you can try cleaning the .wasp
folder and reinstalling all the packages. Run wasp clean
in your terminal to delete all .wasp
and node_modules
stuff, then run wasp start
to reinstall everything.
If you continue to experience this issue, it would be helpful to know how you got into this state. If you can identify what specific scenario causes that, it can help in trying to mitigate that[^1^].
^1^]: [Source (https://discord.com/channels/686873244791210014/1215750573278629958)
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @ArjunSohur, 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?Cool, thanks. I was stressing for a second
Wohooo @ArjunSohur, you just became a Waspeteer level 2!
@ArjunSohur what helped you at the end, I am guessing
wasp clean
? Anyway you can replicate that state you got into -> if so, we would love to try to reproduce it on our side.iirc, it happened when I did npm install lucide-react
Thanks! That might help us.
No problem!