Google Git
Sign in
chromium/devtools/devtools-frontend/de62a03a98e717d7fbccc69d597fec67dbfdebf9
commit
de62a03a98e717d7fbccc69d597fec67dbfdebf9
[log]
author
Thiago Perrotta <tperrotta@chromium.org>
Fri Jul 29 18:32:10 2022
committer
Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>
Tue Aug 02 05:01:11 2022
tree
03f254e1256e2c970692450c63ec2533aa0d9759
parent
513bcd34bff66e3260339c1f818373eab79762f1 [diff]
add `gn gen out/Default` prebuild as a pre-req of `npm run build`

Running `npm run build` (autoninja) before running `gn gen` yields an
error message as `out/Default` doesn't exist.

Ensure `gn gen out/Default` always runs prior to `npm run build` by
adding it as a prebuild script.

Furthermore refactor manual autoninja invocations to use `npm run
build` for consistency and also to take advantage of the newly added
prebuild script.

Before: `npm run build` fails in a fresh clone
After: `npm run build` succeeds in a fresh clone
Bug: None
Change-Id: I9dceaab3b1ee4cd8ec16f10ddd604a38e64420aa
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3792926
Auto-Submit: Thiago Perrotta <tperrotta@chromium.org>
Reviewed-by: Mathias Bynens <mathias@chromium.org>
Commit-Queue: Thiago Perrotta <tperrotta@chromium.org>
1 file changed
tree: 03f254e1256e2c970692450c63ec2533aa0d9759
  1. .vscode/
  2. build_overrides/
  3. config/
  4. docs/
  5. extension-api/
  6. front_end/
  7. inspector_overlay/
  8. node_modules/
  9. scripts/
  10. test/
  11. third_party/
  12. v8/
  13. .clang-format
  14. .editorconfig
  15. .eslintignore
  16. .eslintrc.js
  17. .gitattributes
  18. .gitignore
  19. .gn
  20. .mailmap
  21. .npmignore
  22. .npmrc
  23. .style.yapf
  24. .stylelintignore
  25. .stylelintrc.json
  26. ARCHITECTURE.md
  27. AUTHORS
  28. BUILD.gn
  29. codereview.settings
  30. DEPS
  31. LICENSE
  32. OWNERS
  33. package-lock.json
  34. package.json
  35. PRESUBMIT.py
  36. README.md
  37. tsconfig.json
  38. WATCHLISTS
README.md

Chrome DevTools frontend

npm package

The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.

Source code

The frontend is available on chromium.googlesource.com.

Design guidelines

Please be aware that DevTools follows additional development guidelines.

Issue triage

The issue triage guidelines can be found in docs/triage_guidelines.md.

Workflows

Instructions to set up, use, and maintain a DevTools frontend checkout can be found in docs/workflows.md.

Additional references

Source mirrors

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.

Getting in touch