beta.11-webpack.8 visual studio code debug

[tamasfoldi]

Hi!

I'm trying to debug my angular-cli@beta.11-webpack.8 generated project with Visual Studio Code Debugger for Chrome on Windows 7, but I'm not able to hit any breakpoint. The debugger connects to the browser but, does not hit the breakpoint.
I have found this solution for webpack but how can I configure it with angular-cli?

Thanks for the replies!

[santoshsas]

+1
Have generated angular 2 project using angular-cli@webpack
Can someone please let know without webpack.conf how do i configure Vscode to debug with chrome extension on windows 10.
@tamasfoldi have u figured it out?

[tamasfoldi]

@santoshsas No I was not able to solve it, hope there will be a solution cause it is frustrating a little bit.

[santoshsas]

@tamasfoldi yep it is but i believe u can debug in chrome developer tool itself only not in VsCode

[tamasfoldi]

Yes I can but finding the correct .ts is not easy. Maybe something with the source map or I don't know but by default chrome gives me the bundles even in development build. I don't think this is the way it should work. Or am I missing something?

[jzoss]

+1.. Yes I just discovered this issue as well.

[ajrauen]

+1

[jsmucr]

+1

[yuri1969]

+1

[gitonworld]

+1

[daverupp]

same issue, I am not able to attach the debugger from visual studio code. Please have a look into it - I would really appreciate to use angular-cli to work with, but without IDE support in breakpoints, it is a little bit cumbersome.

thanks for help

[tamasfoldi]

maybe it relates to this @filipesilva #1798 (i hope because that means it is going to be fixed)

[yuri1969]

I've just solved this issue after an hour of experimenting. It might be useful for you too: #2453

[tamasfoldi]

Thanks it is working! Should I keep it open so they can do with this something or it is not a bug and this is the proper way how we should configure vs code?

[yuri1969]

@tamasfoldi The current solution seems a bit hardcodish to me. I'm not sure if changes are required in angular-cli or vscode-chrome-debug VSCode plugin.

[tamasfoldi]

@yuri1969 Ok then I will not close it. Thanks again for your workaround

[filipesilva]

I'm going to close this issue in favor of #2453 because it contains some more investigation and a couple of solutions.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}