RollupError
I try to deploy but I have this error:
I saw your issue here: https://github.com/wasp-lang/wasp/issues/1830
But I don't know how to fix it
What am I doing wrong?
GitHub
Prevent rollup errors from leaking to the client · Issue #1830 · wa...
Removing an export of a Query leaks the Rollup error through Wasp output. The error is long and not really informative to the user: [ Server ] [ Server!] [!] RollupError: "createTask" is ...
6 Replies
Wohooo @Estelle, you just became a Waspeteer level 3!
Hi @Estelle. 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 error message you're seeing suggests that Rollup, the module bundler used by Wasp, is unable to resolve a module path. This could be due to a variety of reasons such as incorrect file path, missing dependencies, or a misconfiguration in your project.
Unfortunately, the knowledge sources provided do not contain specific information on how to resolve this particular error. I would recommend checking the file paths in your project and ensuring all dependencies are correctly installed.
For more information on how to troubleshoot issues with Wasp, you can refer to the Wasp documentation (https://wasp-lang.dev/docs).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Estelle, 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?
found my solution here : https://github.com/vitejs/vite/discussions/14237
GitHub
RollupError: Could not resolve · vitejs vite · Discussion #14237
I'm getting the above error that says it can not resolve my CSS files in my react Typecript file. The project works fine local, but breaks when I try build and deploy through Github. I would ap...
@Estelle, glad it worked out for you!
Thanks for including the solution. So it was a casing issue in the end? 😅
Yes only that and I had to read it 10 times to see it 😬
Ouch, I feel you 😄
Happens to me a lot. Another one that's similar and tough to spot is swapping two letters in a word, for example
initialize
vs initailize
. Gets me every time