Remove dependency on Chrome ScriptID
- Dominant language
- Dart
- Stars
- 224
- Forks
- 94
- Avg merge
- 7h 14m
- Merged PRs (30d)
- 2
Description
As of https://github.com/dart-lang/webdev/pull/1078 we no longer require the scriptID to set breakpoints. However, we still depend on the scriptID provided in the JS frames to translate them to Dart frames. However, the script URL is also provided in the JS frames which should provide enough information to do the translation. Removing our dependency on the script ID will greatly improve the IPL of Dart DevTools as we will no longer saturate the Debug Extension connection with these `ScriptParsed` events.
Contributor guide
Research direction
Start by tracing how JavaScript frames are translated to Dart frames and where the frame script URL and ScriptID are consumed. Confirm the translation can use the script URL alone, and verify that the workflow no longer depends on ScriptParsed events or saturates the Debug Extension connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- devtools
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100