[scopes] Record mapping positions for method scopes According to the spec, we should prefer the start of the identifier as the named mapping position, but we can also use the opening parenthesis. Because Acorn doesn't maintain parent pointers, we have to stash the mapping locations for 'MethodDefinition' nodes on the ScopeAnalysis class. This is because the "value" node of a 'MethodDefinition' is a 'FunctionExpression', which in turn records the actual `Scope`. Note that methods for object literals are not handled this way. That is because they go via a `Property` AST node. `MethodDefinition` only exists inside classes. [email protected] Bug: 433162438 Change-Id: Iaf7bd7840c1ee17f364df9f7b484a4e36116f172 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/7247666 Reviewed-by: Benedikt Meurer <[email protected]> Auto-Submit: Simon Zünd <[email protected]> Commit-Queue: Benedikt Meurer <[email protected]>
The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com. Check out the Chromium DevTools 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.
There are a few options to keep an eye on the latest and greatest of DevTools development:
Follow What's new in DevTools.
Follow Umar's Dev Tips.
Follow these individual Twitter accounts: @umaar, @malyw, @kdzwinel, @addyosmani, @paul_irish, @samccone, @mathias, @mattzeunert, @PrashantPalikhe, @ziyunfei, and @bmeurer.
Follow to g/[email protected] mailing list for all reviews of pending code, and view the log, or follow @DevToolsCommits on Twitter.
Checkout all open DevTools tickets on crbug.com
Use Chrome Canary and poke around the experiments.