Errors with tsconfig
Hello! I am currently running the saas wasp template for the very first time and I faced this problem:
My setup is:
Thanks for your help
4 Replies
Hi @Jorge Alemán. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
The error message you're seeing suggests that there's an issue with your
tsconfig.json
file. Specifically, it seems like the file @tsconfig/node18/tsconfig.json
is not found, and there are also issues with finding type definitions for 'jest' and a module 'rollup/parseAst'.
From the knowledge sources, there are a few discussions around tsconfig.json
files in Wasp projects. In one Github issue (https://github.com/wasp-lang/wasp/issues/1430), it's mentioned that the Wasp team is figuring out how to handle tsconfig
files in user projects. In another Github issue (https://github.com/wasp-lang/wasp/issues/939), it's suggested that Wasp should manage tsconfig.json
files, checking if they exist, regenerating them if they don't, and fixing them if something is wrong.
Based on these discussions, it seems like your issue might be related to the management of tsconfig.json
files in Wasp. However, without more specific information on how Wasp handles these files, it's hard to provide a definitive solution.
As a first step, you could check if the tsconfig.json
file exists in your project and if it's correctly configured. If it doesn't exist or if it's misconfigured, you might need to regenerate it or fix the configuration.
If the issue persists, I would recommend reaching out to the Wasp community or the Wasp team directly for more specific guidance. They might be able to provide more insights based on the specific error messages you're seeing.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Jorge Alemán, 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?Could you maybe try with Node 20 🙂
nvm use 20
wasp clean
wasp start
It's an issue we are actively investigating, sorry about that.
cc: @martinsosI added the dev dependency and then it worked.
Node 20 without the dependency worked, thanks @miho !
Yup, thanks for the report, this just started happening a couple of days ago, we will be jumping on it in the following days!
@Jorge Alemán this might help us fix it: what is your OS?