It looks to me as though I have to somehow get inside the webpack dev server. I'm able to debug a node.js app generated by express, and it generates its own debug port along the lines of: /home//.nvm/versions/node/v13.13.0/bin/node -inspect-brk=11875 bin/www When I stop the dev server, either by using the run bar or closing the browser, the terminal tells me I've stopped and the breakpoint returns to its solid red appearance. Note that the browser is open on my Windows 10 host. To create a production build, use npm run build. Note that the development build is not optimized. You can now view home-react-app in the browser. The built-in terminal contains: Compiled successfully! The "DEBUG CONSOLE" contains: Waiting for update signal from WDS.Äownload the React DevTools for a better development experience. While the development server is running, the breakpoint is a hollow circle, and its tooltip reads "Breakpoint set but not yet bound". When I start the app from "Run" menu, the development server starts, a chrome browser opens, and the resulting page has the spinning React logo and reads "Edit src/App.js and save to reload." The breakpoint is ignored. 1 Am using below Twitter Bootstrap cnd it is working well with Firefox ,chrome and IE browsers but problem with Safari 5.1.7 browser as well as Iphone 6. "runtimeExecutable": "$/node_modules/.bin/react-scripts", Hover to view descriptions of existing attributes. Use IntelliSense to learn about possible attributes. I've installed the "Chrome development extension". I've done all sorts of permutations of launch.json and package.json, none seem to make any difference at all. I've set a breakpoint at line six of the App.js generated by create-react-app. I'm new to this technology stack so please forgive my newbie confusion. Other projects within the same solution can debug normally, but only this project skipped breakpoints during debugging. I use the "Remote SSH" extension of VSCode and it seems to mostly work. I encountered this issue after unloading and reloading a unit test project (MSUNIT), and the debug didn't stop at any breakpoints and skipped all of them, but the tests were running fine. Im using igGrid on another page with the exact same behaviour, IE/Chrome/Firefox are fine, Safari does not call the update url. I use VSCode on a Windows 10 Pro host connected to a Centos 7 system running on a guest VM using VMWare. I'm unable to make VSCode stop at a breakpoint on the app created by npx create-react-app on a guest VM running on the same system as VSCode.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |