where is JETBRAINS IDE SUPPORT chrome extension... it cant be found anywhere now on the internet Follow Meanstack Created February 23, 2021 12:58 where is JETBRAINS IDE SUPPORT chrome extension... it cant be found anywhere now on the internet
The Chrome extension was removed from the store intentionally and we have no plans to bring it back.
The extension is not required for debugging since v. 2017.3; in the past couple of years, we were not recommending using it.
With Chrome 86 (released on October 6, 2020) and higher, the extension no longer works properly and we at JetBrains have no intention to update the extension to work with the new Chrome versions.
WebStorm 2020.3 removed the option to use the extension for debugging from the IDE Preferences.
Thank you Elena for quick response
So has this debugging option been substituted for a better one?
Can you elaborate on how we would debug using the IDE now without the extension?
Or is this a termination of IDE debugging altogether and we have to find a new debugger and no alternative?
What do former IDE Support Extension users do now to debug like we se to with the extension?
JetBrains IDE is better than vscode
What cant they fix this? unless there is a new substitute?
if there is a new substitute where are the docs?
I need to KNOW something here I relied on that for professional consulting for years
dont let vscode and chrome take over
WEBStorm is better
Is there documentation on HOW to debug within the IDE without the extension?
I dont want chrome devtools
I want JetBrains IDE debugger stepping thru my typescript
>Is there documentation on HOW to debug within the IDE without the extension?
Trying to attach debugger on a project based on Preact, The editor produces an extra tabs similar to the recently edited code, and browser is slow to update changes or not at all from changed code in WebStorm any hints on what to do ?
FWIW: https://www.jetbrains.com/help/pycharm/angular.html#angular_running_and_debugging_debug is the replacement I was looking for. There's a generated Angular Application in your run/debug configurations when you add the angular facet. It's not correct to debug the Angular CLI Server.
Elena Pogorelova Your suggestion to map source to URL solved the problem