Can only hit breakpoints in source view if there is a debugger statement in the code
Reported by
ryanvic...@gmail.com,
Nov 19
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Steps to reproduce the problem: 1. Use a create react app based application 2. Map a workspace 3. Set a breakpoint 4. Change your code 5. Refresh browser What is the expected behavior? Execution stops at breakpoint What went wrong? Execution doesn't stop Did this work before? N/A Chrome version: 70.0.3538.102 Channel: stable OS Version: OS X 10.13.6 Flash Version: If you add a debugger statement to the code then after it hits that debugger statement the other dev tools breakpoints will start working.
,
Nov 20
ryanvicetx@ Thanks for the issue. Request you to provide a sample file/URL where this issue can be reproduced, which will help in further triaging. Thanks..
,
Nov 20
As I mentioned in step (1) just setup a create react app based app and try and hit a break point. You can get the directions for setting up a create-react-app from the github pages readme: https://github.com/facebook/create-react-app
,
Nov 20
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 26
ryan are sourcemaps enabled on CRA and flipped on in devtools? Does this start working if you flip off JS sourcemaps in the devtools settings?
,
Nov 27
Paul, Yes both are enabled and flipping off JS source maps in devtools doesn't help. Please find an example of the bug in the attached gif. Note that I've been using this workflow for a really long time.
,
Dec 4
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, Nov 20