-
Notifications
You must be signed in to change notification settings - Fork 12k
Issue debugging beta.18. Sourcemap issue? #2909
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
Having this issue as well. It seems a 2-3 lines offset for me. |
I have the same problem too, hits the break-point then when I attempt to step over it jumps to somewhere completely random. |
after updating the project I was able to get this working again by going back down to beta.15 of just the cli. |
Thanks @zackarychapple , did you change to beta.15 both globally and in the project? |
@EricBichara just the project. |
See the fix in #2811 from @un33k - this has been fixed in master for the next release. un33k commented 6 days ago • edited |
@chadbr Thanks, modification of node_modules/angular-cli/models/webpack-build-development.js helped. |
Fixed in #2857 |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This change adds the `--verbose` option to the SSR dev server. closes angular#2909
OS?
Mac OSX 10.12.1
Versions.
angular-cli: 1.0.0-beta.18
node: 6.8.1
os: darwin x64
Npm: 4.0.0
Chrome: 54.0.2840.71
Repro steps.
new project created with "ng new testproject". Changed only to the following code in app.component.ts
In chrome dev tools, breakpoint doesn't seem to match the scope

I've tested in my other projects which i've updated to beta.18, get the same issue.
Also tried reinstalling angular-cli to make sure there where no issues there:
npm uninstall -g angular-cli
npm cache clean
npm install -g angular-cli
ng new testproject
The text was updated successfully, but these errors were encountered: