AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Webstorm react debug1/11/2024 ![]() We attempt to use the default port but if it is busy, we offer the user to Process.on('unhandledRejection', err => = require('react-dev-utils/browsersHelper') ĬheckBrowsers(paths.appPath, isInteractive) terminate the Node.js process with a non-zero exit code. In the future, promise rejections that are not handled will Makes the script crash on unhandled rejections instead of silently Do this as the first thing so that any code reading it knows the right env. I know it's not much to go on but I am dead in the water. The only thing I did in the meantime was, I believe, kill an errant process on port 3002. It's frustrating, as it was working perfectly. (I tried it both with 'ensure breakpoints' not checked, as I had it originally, as well as checked - no difference)Īnd the actual script is at the end of this post (it is a long script which I didn't write and don't understand). I tried restarting WS, as well as creating a new debug config (see screenshot) I need to click the red square again to stop everything ![]() ![]() The weird thing is that when I click on the little red box to stop the process, then the little bug icon lights up with a green dot on the bottom (it's debugging) and a new tab opens up in the Chrome instance. Neither does it stop on breakpoints (see screenshot) All was going well and then - changing nothing - it stopped working.īy "stopped working" I mean that when I click on the little debug icon in the toolbar the app starts up and loads in the custom Chrome instance (I quit Chrome between debug sessions, as instructed), and the little 'stop' square lights up. It connects to a custom Chrome instance - custom, so that I can retain my particular Chrome setup (Redux Dev Tools, etc) in the instance opened by the debugger. I have WebStorm set up to debug a React app using a Javascript Debug configuration.
0 Comments
Read More
Leave a Reply. |