Change describeWithEnvironment to setup/teardown globals per-test Modify `describeWithEnvironment` to initialize and deinitialize global variables in `beforeEach` and `afterEach` hooks instead of suite-level `before` and `after` hooks. This ensures a clean environment state for every test and prevents global leakages/pollution across tests. For test suites that require persistent suite-level environment setup (e.g., due to trace loading or asynchronous widget updates), migrate them to use plain `describe` blocks with explicit `before` and `after` hooks that call `initializeGlobalVars()` and `deinitializeGlobalVars()`. Bug: 493763857 Change-Id: I44202a49542b7cf762fe8b2c84cfd3e5e6f0385d Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/8020647 Auto-Submit: Simon Zünd <szuend@chromium.org> Commit-Queue: Mathias Bynens <mathias@chromium.org> Reviewed-by: Mathias Bynens <mathias@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.