You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently set breakpoints by script ID. This has a number of drawbacks, especially around re-establishing breakpoints. There is an API to set breakpoints by URL. This API has the benefit of persisting across reloads.
Sets JavaScript breakpoint at given location specified either by URL or URL regex. Once this command is issued, all existing parsed scripts will have breakpoints resolved and returned in locations property. Further matching script parsing will result in subsequent breakpointResolved events issued. This logical breakpoint will survive page reloads.
Would the URL point into the .js file or would it consider a source map? What happens if the JS code is shifted around in the reload, does that cause any issues?
The URL would point to the containing module of the Dart file which would be a .js file. If the code get's shifted around we would have the same issue as Chrome does today which sets breakpoints as a per line basis.
Activity
natebosch commentedon Jul 27, 2020
Would the URL point into the
.jsfile or would it consider a source map? What happens if the JS code is shifted around in the reload, does that cause any issues?grouma commentedon Jul 28, 2020
The URL would point to the containing module of the Dart file which would be a
.jsfile. If the code get's shifted around we would have the same issue as Chrome does today which sets breakpoints as a per line basis.Set breakpoints by regex URL (#1078)