-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Request: hit breakpoints in browser dev tools #425
Comments
+1 Breakpoints don't work in constructors or event hooks (like OnInit, AfterViewInit, etc...). For me, they do work during regular method callbacks. If a new non-event lifecycle breakpoint is not being hit, refresh the page and it should. (using beta 9 and Chrome dev tools) |
same here, using the new setup, my breakpoints are not working anymore. Perhaps something to do with the sourcemaps implementation used? |
We definitely found some differences with sourcemap. Initially we tried with Then we tried with (slower) |
@BrainCrumbz : I can also confirm this |
Just to clarify, I used cheap-module-eval-source-map. From Chrome Dev Tools, when I clicked in main.bundle.js to set a break point, I expected Chrome to open open my class (in typescript). The break point would land on the ugly javascript in main.bundle.js. But who can read this? I followed @BrainCrumbz suggestion. I'm able to click in the javascript source and Chrome resolves the breakpoint in the respective typescript class. Thanks, @BrainCrumbz ! |
You're welcome! Happy to be helpful @largeDachshund |
@BrainCrumbz are you able to hit breakpoints with "sourcemap" when using HMR ? Initial state after starting Breakpoint is set. I add |
Sorry, we're not using this starter at the moment, and I've not checked back this issue recently. Maybe someone else more up-to-date with the project can reply. |
sorry this may sound super rule but I'm closing long standing issues and refactoring the codebase. If you run into this problem again feel free to open another issue |
[ ] bug report
[x] feature request
[ ] question about the decisions made in the repository
When serving in development mode (
npm start
), one can open browser onhttp://localhost:3000/
. When setting a breakpoint, e.g. in home.ts, and reloading page, execution should pause on that line.Breakpoint seems to be ignored. Execution proceeds beyond that. Client app runs normally, no particular errors.
Execution should pause on breakpoint set.
Debugging purposes.
The text was updated successfully, but these errors were encountered: