my website built with wasp showing black
after i built everything completely i ran wasp start and i keep getting a blank page
2 Replies
Hi @Mitini ⚙ ☁. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
A blank (black) page after running wasp start is a common issue and can be caused by several factors. Here are some steps and checks based on the knowledge sources:
1. Check for Errors in Terminal and Browser Console
Run wasp start and look for any errors in the terminal where you started Wasp. Also, open your browser's developer tools (F12) and check the console for errors. These errors can provide clues about missing modules, incorrect imports, or build issues. For example, an error like "The requested module ... does not provide an export named 'Link'" indicates an incorrect import statement in your code. In this case, you should import Link from wasp/client/router, not wasp/client/operations. Fixing such import errors can resolve the blank page issue Discord: nothing shows up in localhost:3000 after wasp start. 2. Run wasp clean
Sometimes, stale build artifacts can cause issues. Try running: This will clean up generated files and rebuild your app, which often resolves blank page problems Discord: nothing shows up in localhost:3000 after wasp start. 3. Check File System Location (WSL2 Users)
If you are using WSL2 and your project is located on the Windows file system (e.g., /mnt/c/...), hot reloading and file change detection may not work properly, which can lead to issues like a blank page. Move your project to the Linux file system (e.g., under /home/username) to avoid this problem Github Issue: File changes not detected by wasp start in WSL2. 4. Check for Incorrect Imports or Paths
If you generated your app using Mage or another AI tool, it may have introduced incorrect imports or file paths. For example, importing modules from the wrong location or missing the correct path in your main.wasp file can cause the frontend to fail to load. Double-check your import statements and page/component paths Discord: nothing shows up in localhost:3000 after wasp start. 5. Port Conflicts
Ensure that nothing else is using port 3001 (backend) or 3000 (frontend). If there is a conflict, terminate the other service and restart your app Discord: nothing shows up in localhost:3000 after wasp start. If you follow these steps and still see a blank page, please provide: - Any error messages from your terminal and browser console. - Your OS and Wasp version. - How you created your app (starter, Mage, etc.). This information will help further diagnose the issue. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @Mitini ⚙ ☁, 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?
Run wasp start and look for any errors in the terminal where you started Wasp. Also, open your browser's developer tools (F12) and check the console for errors. These errors can provide clues about missing modules, incorrect imports, or build issues. For example, an error like "The requested module ... does not provide an export named 'Link'" indicates an incorrect import statement in your code. In this case, you should import Link from wasp/client/router, not wasp/client/operations. Fixing such import errors can resolve the blank page issue Discord: nothing shows up in localhost:3000 after wasp start. 2. Run wasp clean
Sometimes, stale build artifacts can cause issues. Try running: This will clean up generated files and rebuild your app, which often resolves blank page problems Discord: nothing shows up in localhost:3000 after wasp start. 3. Check File System Location (WSL2 Users)
If you are using WSL2 and your project is located on the Windows file system (e.g., /mnt/c/...), hot reloading and file change detection may not work properly, which can lead to issues like a blank page. Move your project to the Linux file system (e.g., under /home/username) to avoid this problem Github Issue: File changes not detected by wasp start in WSL2. 4. Check for Incorrect Imports or Paths
If you generated your app using Mage or another AI tool, it may have introduced incorrect imports or file paths. For example, importing modules from the wrong location or missing the correct path in your main.wasp file can cause the frontend to fail to load. Double-check your import statements and page/component paths Discord: nothing shows up in localhost:3000 after wasp start. 5. Port Conflicts
Ensure that nothing else is using port 3001 (backend) or 3000 (frontend). If there is a conflict, terminate the other service and restart your app Discord: nothing shows up in localhost:3000 after wasp start. If you follow these steps and still see a blank page, please provide: - Any error messages from your terminal and browser console. - Your OS and Wasp version. - How you created your app (starter, Mage, etc.). This information will help further diagnose the issue. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @Mitini ⚙ ☁, 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?
hi @Mitini ⚙ ☁ can you paste here the logs in your terminal and in the browser console?