10:13:27,763 INFO - rowsers.BrowserLauncherAppless - Timed out 10:13:16,176 INFO - initialization complete console.WebConsoleHistoryView - WebConsole page initialization complete 10:13:16,172 INFO - WebConsole page loaded script.IdeScriptEngineManager - initialized in 114 ms 10:12:30,949 INFO - 5SchemaProvider - HTML5_SCHEMA_LOCATION = C:/Program Files/JetBrains/WebStorm 2020.2.1/lib/intellij-xml.jar!/resources/html5-schema/html5.rnc 10:12:27,631 INFO - ion.PackageVersionRangeMatcher - Matching 61 done in 208 ms 10:12:26,534 INFO - gnostic.WindowsDefenderChecker - Windows Defender status: not used 10:12:22,798 INFO - indexing.UnindexedFilesUpdater - Unindexed files update started: 0 files to index diagnostic.PerformanceWatcher - Indexable file iteration took 1088ms general responsiveness: ok EDT responsiveness: ok diagnostic.PerformanceWatcher - Pushing JS language level to 115 libraries took 1308ms general responsiveness: ok EDT responsiveness: 1/2 sluggish diagnostic.PerformanceWatcher - Pushing properties took 251ms general responsiveness: ok EDT responsiveness: ok 10:12:21,384 INFO - cloudConfig.CloudConfigManager - = StatusBar.start create = diagnostic.PerformanceWatcher - Post-startup activities under progress took 751ms general responsiveness: ok EDT responsiveness: 1/1 sluggish Chrome always starts with a blank page and i am unable to debug anything. Add the remote-debugging-port option manually with port 52421 and used another chrome-user-data folder. What i have tried so far:Ĭhanged the path directrly to chrome.exe under Tools -> Web Browsers. My guess the chrome instance is not started with the -remote-debuging-port option. I only see the SYN_SEND from my webstorm instance. Thats correct on Windows 10 i cannot find any open port 52421 on any started chrome instance using netstat -ano. Please ensure that the browser was started successfully with remote debugging port opened. Port cannot be opened if Chrome having the same User Data Directory is already launched. Waiting for connection to localhost:52421. I tried adding mapping to the relevant part of the app in the debugger settings (as suggested by webstorm support), but unfortunately, it didn't resolve the issue.Webstorm 2020.2.1 only opens a about:blank page, if i want to debug my angular application. I also tried with the exact path "localhost:3000/apps/foo", but no difference. My debugger in WebStorm is set to "localhost:3000," and I assumed it should catch all paths under that domain, which doesn't seem to be the case. I followed the WebStorm documentation to set up the JavaScript debugger, and while it partially works, I noticed that if the code I try to debug ends up in a path like " the debugger works, but if it is in a path like " the debugger fails to catch the breakpoints. The app works fine when debugging in VS Code, but when I switch to WebStorm, some parts of the app ignore breakpoints, making debugging challenging. The app is structured as a monorepo, and I use pnpm as the package manager. I'm facing an issue with WebStorm's debugging feature while working on my React (TypeScript) app that uses.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |