-
Notifications
You must be signed in to change notification settings - Fork 552
How would you debug in vscode? #92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
What you mean with debug in here? Because |
Ah OK my bad so how would you debug anyway using vscode? any other best approach? I just wasn't being able to produce build anyway to check my unlucky guess due to #93 |
Wrong person to ask, I survive with console.logs and that is definitely not the way to go :/ Better if you ask in SO or other sites, because I cannot be of any help. |
Get bored by Actually I was trying to use this thing https://github.com/Microsoft/vscode-chrome-debug but no luck. I think because of webpack. Haven't dig much in to that after all. Then looked in to this one http://schempy.com/2016/01/19/angular2_webpack_typescript/ but not working for me when trying to set breakpoints in chrome as mentioned in article. UPDATE. Actually the second option is working. I was doing the full page refresh at first which is didn't triggered my break points in chrome dev tools for some reason. But after app is loaded and I tried to click on my route component I set breakpoints on - in such case all my ts breakpoints was getting hit.
|
Will take a peek at both and if I get something interesting, I could update the README here. |
Cool. Checkout my updated update above :/ |
Uh oh!
There was an error while loading. Please reload this page.
Just wondering what is the best approach to debug using vscode?
Should I just run
npm run build
#93 and debugdist
by runninglive-server
or something or there is a better way?The text was updated successfully, but these errors were encountered: