W
Waspβ€’3w ago
Milica

Mage app not working

this is the error 🐝 --- Starting compilation and setup phase. Hold tight... ------------------------ 🐝 --- Compiling wasp project... -------------------------------------------------- ❌ --- [Error] Your wasp project failed to compile: ------------------------------- Failed to parse tsconfig file[eval]:27"compilerOptions": {^ SyntaxError: Unexpected token ':' at new Script (node:vm:94:7) at createScript (node:vm:250:10) at Object.runInThisContext (node:vm:298:10) at node:internal/process/execution:82:21 at [eval]-wrapper:6:24 at runScript (node:internal/process/execution:81:62) at evalScript (node:internal/process/execution:103:10) at node:internal/main/eval_string:30:3 Node.js v18.19.1 ❌ --- [Error] Compilation of wasp project failed: -------------------------------- @Godke Akshay
2 Replies
kapa.ai
kapa.aiβ€’3w ago
Hi @Milica. 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 error message you've provided, it appears that there's an issue with parsing the tsconfig.json file in your Wasp project. This is likely due to a syntax error in the configuration file. Let's break down the problem and suggest a solution: 1. The error message indicates a SyntaxError at the "compilerOptions" section of your tsconfig.json file. 2. The specific error "Unexpected token ':'" suggests that there might be a missing or misplaced character before the colon. To resolve this issue, you should: 1. Open your project's tsconfig.json file. 2. Look for the "compilerOptions" section. 3. Make sure the JSON syntax is correct. For example, it should look something like this:
{
"compilerOptions": {
// options here
}
}
{
"compilerOptions": {
// options here
}
}
4. Check for any missing commas, brackets, or other syntax errors around this section. If you're unsure about the correct structure of the tsconfig.json file, you can refer to the Wasp documentation on IDE support, which mentions that Wasp generates a "dummy" tsconfig.json file for proper IDE support. If the problem persists after fixing the syntax, you might want to try regenerating the tsconfig.json file. There's an open issue in the Wasp GitHub repository discussing the potential need for Wasp to detect and regenerate missing or incorrect tsconfig.json files: Ensure "user" tsconfig.json files exist and are correct. As a workaround, you could try deleting the existing tsconfig.json file and then running wasp new to create a new project, which should generate a correct tsconfig.json file. Then, you can copy your existing code into this new project structure. If none of these solutions work, you may need to seek further assistance from the Wasp community or developers, as there might be a more specific issue with your project setup. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @Milica, 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?
Milica
MilicaOPβ€’3w ago
@Godke Akshay here's what our bot is saying, I'm deleting that message you sent before

Did you find this page helpful?