Your wasp project failed to compile
- The "include" field is missing in tsconfig.json, you must set it to: ["src"].
- Invalid value for the "compilerOptions.outDir" field in tsconfig.json, you must set it to: ".wasp/out/user".
- The "compilerOptions.composite" field is missing in tsconfig.json, you must set it to: true.
- The "compilerOptions.skipLibCheck" field is missing in tsconfig.json, you must set it to: true.
5 Replies
Hi @Amin. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the provided knowledge sources, it appears that Wasp has recently undergone changes in how it handles TypeScript configuration. The error message you're seeing suggests that your
tsconfig.json file needs to be updated to comply with Wasp's current requirements. Here's what you need to do:
1. Open your project's tsconfig.json file.
2. Add or update the following fields:
These changes are necessary because Wasp now uses a single tsconfig.json file for both client and server code, as mentioned in the Migration from 0.11.X to 0.12.X documentation.
It's worth noting that Wasp is still figuring out its TypeScript configuration story. There have been discussions about how to manage tsconfig.json files, as evidenced by the GitHub issue on ensuring "user" tsconfig.json files exist and are correct.
If you're using an older version of Wasp, you might want to consider updating to the latest version, which should provide better TypeScript support out of the box. You can check your current Wasp version and update if necessary.
If you continue to experience issues after making these changes, you may want to try running wasp clean in your app directory and then wasp start to ensure all old configurations are removed and a fresh setup is created.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Amin, 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?I already did try this but not working.
what wasp version are you on @Amin? run
wasp version to see.
also, check that it matches the wasp version in your main.wasp file
@kapa.ai how can a specific version of wasp be installed?Let me check the knowledge base for you again. One moment! :books:
----------------------
To install a specific version of Wasp, you can use the installer script with a version flag. Here's how you can do it:
1. Open your terminal.
2. Run the following command, replacing
x.y.z with the specific version number you want to install:
For example, if you want to install version 0.12.4, you would run:
This command downloads the Wasp installer script and executes it with the specified version flag.
You can find the list of available Wasp versions on the GitHub Releases page.
If you want to check your current Wasp version after installation, you can use the command:
This command will also provide instructions on how to install or switch to different versions of Wasp.
CLI Reference provides more information about Wasp CLI commands, including the version command.
Remember that different Wasp projects might require specific versions, so it's important to use the correct version for your project as specified in the project's configuration.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Vinny (@Wasp), 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?You updated the
tsconfig.json in your project dir file with the values? What does Wasp CLI say when you try to compile again?