14 Replies
Hi @Mohan. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Yes, there is a way to bypass the email verification step in development mode when using Wasp. You can set the
SKIP_EMAIL_VERIFICATION_IN_DEV environment variable to true in your .env.server file. This can be useful when you are developing your app and don't want to go through the email verification flow every time you sign up. Here is how you can do it:
Remember, this is only for development mode and should not be used in a production environment.
For more details, you can refer to the Wasp documentation on Email Verification Flow (https://wasp-lang.dev/docs/auth/email#email-verification-flow).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Mohan, 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?Thanks
@kapa.ai how do i mark this as solved
Let me check the knowledge base for you. One moment! :books:
----------------------
If you're referring to a question or issue on a platform like GitHub or Discord, the process to mark it as solved can vary.
On GitHub, you can close the issue if you opened it. Just click on the
Close issue button at the bottom of the issue page. If it's a discussion, you can mark a response as an answer. Click on the ... button on the comment you want to mark as an answer, then click Mark as answer.
On Discord, there isn't a built-in way to mark a question as solved. However, you can simply send a message stating that your issue has been resolved.
If you're referring to a different platform, please provide more details so I can give a more accurate answer.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Mohan, 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?Solved
@kapa.ai how i run debugger with ths
Let me check the knowledge base for you. One moment! :books:
----------------------
To run a debugger with Wasp, you would typically use the debugging tools provided by your code editor or IDE, such as Visual Studio Code or WebStorm, and the specific debugging process can vary depending on the tool you're using.
For example, if you're using Visual Studio Code, you can set breakpoints in your code and then start a debugging session by clicking on the "Start Debugging" button or by pressing F5.
However, the knowledge sources provided do not contain specific instructions or examples for running a debugger with Wasp. For more detailed instructions, you should refer to the documentation of your code editor or IDE, and the Node.js debugging guide if you're debugging server-side code.
If you're having trouble setting up the debugger with Wasp, feel free to ask for more specific help, providing details about the code editor or IDE you're using, and the part of your Wasp project you're trying to debug.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Mohan, 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?
@miho @sodic can I assume that server debugging is not possible now?
or is there a way to do it?
If you generate your app with Wasp and then run it by yourself i.e. going into the
.wasp/out folder and running the web-app and server manually via npm instead of wasp start you can do what ever you can do with Node.js 🙂 https://nodejs.org/en/learn/getting-started/debugging#enable-inspector
Wasp doesn't support 1st party support for debugging the server - yet, but you can work with Node.js directly to debug some specific issue.Node.js — Debugging Node.js
Node.js® is a JavaScript runtime built on Chrome's V8 JavaScript engine.
I've noted this in a Github issue: https://github.com/wasp-lang/wasp/issues/1998
GitHub
Node.js debugger for the server · Issue #1998 · wasp-lang/wasp
Some users asked how they can debug the server's Node.js app. Ideally, we would enable the users to use the --inspect with a Wasp flag: https://nodejs.org/en/learn/getting-started/debugging#ena...
Make sense. Thanks @miho
Btw, if you're still trying to set up the debugger in the generated app, this thread explains how to do it: https://discord.com/channels/686873244791210014/1134423535310360667/1134423535310360667
Thanks, @sodic . I was able to figure it out. I'm thinking of writing about how I did it this weekend. I'll cross-check this thread, and if I did anything more or different, I'll write about it there
Wohooo @Mohan, you just became a Waspeteer level 2!
@Mohan we'd love it read it, please share when you have the time 🙂
Hey @Mohan, any updates on this one 😄
Thanks!