Blank Page when Create New App
Hi, I am new to wasp and wanted to create an app with open-saas. I followed the instructions on the official docs, but when running
wasp start I get an empty page at http://localhost:3000/ (favicon is popping up, but the page has no content). I don't think this is supposed to happen.
I am running with node version 22.9.0, npm version 10.8.3, wasp version 0.15.0 on a M1 Mac.
There was a warning on running wasp start:
DeprecationWarning: The 'punycode' module is deprecated. Please use a userland alternative instead.
Maybe that is relevant but I am suspecting more of a version issue for node or npm. Which node and npm versions are used by the developer team? I am okay with changing my node or npm version so they align. This looks like an interesting project and I want to get it working.
Edit: I tried to create a todo list app and it worked. Seems like it is an open-saas specific problem.
I have created an issue on https://github.com/wasp-lang/open-saas/issues/2897 Replies
Hi @DavidFeng. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Hello! It's great to hear that you're interested in Wasp and trying out the open-saas starter.
From the knowledge sources provided, it seems that Wasp has had some issues with certain Node versions. For instance, in this Github issue (https://github.com/wasp-lang/wasp/issues/442), it was suggested that Wasp should require Node v16 along with npm 8 due to some odd behaviors with other versions.
However, in another Github issue (https://github.com/wasp-lang/wasp/issues/1526), a user reported an error when using Node 20.8.1, and Wasp required Node ^18.12.0.
Given this, it might be worth trying to switch to Node v16 and npm 8, or Node ^18.12.0, to see if that resolves the issue. You can manage your Node versions with
nvm (Node Version Manager).
As for the DeprecationWarning about the 'punycode' module, it's hard to say without more information whether this is related to the issue you're experiencing.
Lastly, since you mentioned that you've already created a Github issue, that's a great step! The Wasp team or community members might be able to provide more specific help there.
I hope this helps, and best of luck with your Wasp project!
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @DavidFeng, 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?@DavidFeng Can you try in incognito or with another browser clean of extensions (happened to me)?
In your issue there is a chrome extension at first line, its: https://chromewebstore.google.com/detail/simple-allow-copy/aefehdhdciieocakfobpaaolhipkcpgc
(Maybe it will help)
Simple Allow Copy - Chrome Web Store
Allow Copy on every website
@DavidFeng are you definitely running the db, and if so did you migrate the db?
Sometimes uBlockOrigin blocks some of the components (but only in dev!) so I'd advise disabling ad blockers on
localhost.
But usually, the generic debug process should be when you are seeing a blank page:
1. Are there any errors in the browser console?
2. Are there any errors in the terminal where wasp start is running?
3. Checking the docs one more time.
4. Pinging us here with all the info as you did 🙂 I'd advise maybe going to step 1 to see if there are some hints as to why the app brokeUpdate: It was the browser extension! Incognito mode worked just fine and everything was fixed after I removed the Chrome Extension. The DB was running normally and there were no error (or abnormal logs) from the Chrome developer console.
Ok! I added a GH issue for this, thanks for letting us know: https://github.com/wasp-lang/open-saas/issues/292 .
GitHub
Avoid page getting blocked by uBlock browser extension · Issue #292...
This issue describes the problem: #289 . It seems that when you create new open-saas app, uBlock chrome extension will block it so just white screen shows, confusing new users. We should figure out...