commit | e6a39dc6883116a1f8c125de1a446cefb9b6bba3 | [log] [tgz] |
---|---|---|
author | Benedikt Meurer <[email protected]> | Mon Aug 19 15:28:26 2024 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Aug 19 16:04:20 2024 |
tree | 62485940578460392b00e8788c1d4ae283103fae | |
parent | b4affbaf3ecaf618edc3c107ff7caa8ef116958b [diff] |
[scripts] Provide a single `npm run lint` command. This unifies the current set of two dedicated scripts for running ESLint and stylelint into a single script, with a single npm run-script command. We need to migrate the Infra and devtools-internal before we can fully remove the old scripts. Bug: 360832181 Change-Id: Ifb98d882d951fb3e1c9d7ff8aae22c8d844ced55 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5796886 Commit-Queue: Benedikt Meurer <[email protected]> Reviewed-by: Philip Pfaffe <[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 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: [email protected]
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools