Angular cli 1.1.1 doesn't allow in-browser debugging

[mdanetzky]

Bug Report

- [x ] bug report -> please search issues before submitting
- [ ] feature request

Versions.

@angular/cli: 1.1.1
node: 8.0.0
os: darwin x64

Repro steps.

ng new debugtest
cd debugtest
ng test
in the browser -> Debug -> developer tools / sources -> cmd+p ->
cannot find app.component.ts!

[LuckyMallari]

see solution here:
#6623

[mdanetzky]

I'm not sure if creating / modifying launch.json each time you make a new project suffices as a solution. Older vesions of angular cli are much more user friendly in that regard.

[filipesilva]

Yeah I agree, this sounds like a different issues as well. This one isn't related to VSCode. It sounds like there is a regression with the sourcemaps.

[filipesilva]

I followed your steps and could see app.component.ts:

I think #6682 fixed it, as per @clydin's comment #6623 (comment).

[mdanetzky]

I still cannot see the sources. Even after the update to Angular cli 1.2.0. Maybe it is the OSX issue.

[filipesilva]

What version of chrome are you using? I'm on 59.0.3071.115.

Can you try making a new app and checking there if you can see the sources? If so, it might be a dependency issue.

[mdanetzky]

Chrome: 59.0.3071.115 (Official Build) (64-bit)
After ng new; ng test:

[filipesilva]

Ok, I think I see what's wrong. Thank you for taking the time to debug.

[filipesilva]

#6862 should fix this I believe. If it doesn't and you still experience this problem after it's merged and released, please let me know.

[AlexLnz]

I just tried updating to 1.2.1 and I get still no sources.

[filipesilva]

@AlexLnz can you tell me exactly how to reproduce what you're seeing? I've been testing this myself and see the sources in devtools.

[AlexLnz]

I'm doing a "ng test". Then in Chrome on the karma page click "Debug".
New page with "Karma DEBUG RUNNER" opens and the tests run again.
Open Chrome Dev Tools (F12).
Go to "sources".
=> Cannot find any ts file there.

Using Chrome 59.0.3071.115

[filipesilva]

@AlexLnz see #6862 (comment)

[dawidjanusz]

Solution:

1. open chrome dev tools(F12),
2. go to "Sources" Tab,
3. refresh page (don't close dev tools).

Regards,
Dawid

[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.}