7/30/2023 0 Comments Vscode reactxpNow when we navigate to the problematic page we see this error. This opens the browser at localhost:3000 as defined in launch.json. Since we know that we need to debug the code we use the VS Code debugger to start a Chrome instance. So first we run the app on our local machine. The error message in production doesn’t tell us a lot. With the right debugging approach we can probably fix this bug in no time. Obviously, our managers are going crazy as well.īut we as the developers stay calm. They’re paying good money and rely on our app. One of the most important pages used to look like this ( you can see a deployed version of it here):īut suddenly we get reports that something is broken ( here a deployed version):ĭamn, how did this bug make it into production? Our customers are upset. Let’s imagine the following situation: We’re a developer working on a Next.js app that is in production. If you’re not familiar with that you can see an example below. You can now use the debugger as you would in the Chrome dev tools.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |