Polyfill.js code file always opens in vscode

Ionic Framework ionic-v3
1

Hello All!!

I am in the middle of developing an Ionic 1 app for my work and I am looking into Ionic 2, so I have some experience with ionic. Here is my issue.

I am using visual studio code for development. I created a ionic 2 sidemenu app. I used the ionic serve command to serve the app to the chrome browser. After that I created a configuration in the launch.json file to attach to chrome for debugging. This is how I have been debugging in vscode for my ionic 1 app and it works great.

The issue is when I change any code in any .ts or .html files. Of course ionic automatically sees that I changed the code and then recompiles and updates the app and refreshes the page in the chrome browser. Every time it does this, vscode opens up the polyfill.js code file in a tab and the code stops somewhere in the polyfill.js code file. I then have to click play in vscode to continue. This is incredibly annoying and slows down development.

Anybody have experience with this and have a fix for this?

Launch Config Attach:

{
    "name": "Chrome Attach",
    "type": "chrome",
    "request": "attach",
    "sourceMaps": true,
    "port": 8200,
    "url": "http://192.168.1.9:8200",
    "webRoot": "${workspaceRoot}/src"
}
2

Hmm, it’s a bit different for V2, since there is more compileing happing (going from TS to JS)
I’m not sure that the VSCode folks have updated the extension for this, so I dont think it’s possible at the moment.
But you can always open up chrome and debug from the chrome dev tools directly.

3

Yes, I can indeed debug in chrome. But I like the debugging experience in vscode much better. I have created a starter project before and got debugging to work without the issue of the polyfill.js file tab popping up all the time. I don’t know if its something I did and just dont realize it or if its a bug that has just been introduced. I will create another starter project and try to debug and see what happens. I will post my findings.

4

It’s due to an uncaught exception. Just uncheck “uncaught exception” it will stop hanging/pausing