Parse relative URLs inside parentheses without function names Some frameworks/libraries override Error#stack to print location strings enclosed in parentheses even when there is no preceding function name (e.g. "at (foo.js:10:5)"). Standard V8 only emits "at functionName (foo.js:10:5)" (with function name and parens) or "at foo.js:10:5" (no function name, no parens). This change updates DetailedErrorStackParser to explicitly handle stack frames where the location string is entirely enclosed in parentheses. By adding a check for content that starts and ends with parentheses when no function name is detected, the parser can now correctly strip them and extract the location. This prevents parsing failures on overridden error stacks. Bug: 485142682 Change-Id: I0f176ae16afee8bb32d79c76ed7299a979803deb Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/7924667 Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by: Eric Leese <leese@chromium.org>
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/devtools-reviews@chromium.org 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.