[scopes] Mark shadowed variables as 'unavailable' This CL changes 'allVariablsInCallFrame' and 'allVariablesAtPosition' to mark original names as 'null' when the underlying compiled name was shadowed. Otherwise we'd use the wrong variable after substitution. Note that we do not yet report failures to the UI and all use-sites currently fall back to using the original expression. Drive-by: Type worker params as `unknown` internally. Ideally we'd have a helper type for "structured cloneable" going forward. R=jarin@chromium.org Bug: 1444349 Change-Id: Id0040eacaf8076fd1ee62f9a08edfe26bc12dc49 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4707975 Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org>
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com.
Check out the project documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.
DevTools frontend repository is mirrored on GitHub.
DevTools frontend is also available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES modules, so consuming this package in other tools may require some effort.
The version number of the npm package (e.g. 1.0.373466) refers to the Chromium commit position of latest frontend git commit. It's incremented with every Chromium commit, however the package is updated roughly daily.
All DevTools commits: View the log or follow @DevToolsCommits on Twitter
All open DevTools tickets on crbug.com
File a new DevTools ticket: new.crbug.com
Code reviews mailing list: devtools-reviews@chromium.org
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools