commit | d3425b95d0ff161d2615702f7a686cc8702980a7 | [log] [tgz] |
---|---|---|
author | Tim van der Lippe <[email protected]> | Fri Jan 07 13:05:09 2022 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jan 07 14:26:50 2022 |
tree | bd242ea4c91252b1d910b2959db37ad238b6143c | |
parent | 0e801b6732a89ab4ebe3f68368eed618d3c04230 [diff] |
Update unit test NPM dependencies Updates Karma, Mocha and Sinon. [email protected] Bug: none Change-Id: Ia93cdafc646e4d3277e7ce869a7a8b5e66a13f0d Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3372928 Auto-Submit: Tim Van der Lippe <[email protected]> Reviewed-by: Jack Franklin <[email protected]> Commit-Queue: Tim Van der Lippe <[email protected]>
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com.
Please be aware that DevTools follows additional development guidelines.
The issue triage guidelines can be found in docs/triage_guidelines.md.
Instructions to set up, use, and maintain a DevTools frontend checkout can be found in docs/workflows.md.
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: [email protected]
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools