Google Git
Sign in
chromium / devtools / devtools-frontend / 992cc762b6790a7bd1a0d5c12ed0169270ac7dd0
commit992cc762b6790a7bd1a0d5c12ed0169270ac7dd0[log] [tgz]
authorBenedikt Meurer <bmeurer@chromium.org>Mon Nov 14 06:59:00 2022
committerDevtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Nov 14 07:39:17 2022
tree130c15a3adc98a6ca912207427a9aba771365d25
parent2007d2b0a076190fd508a6838c30cab43dbc95e3 [diff]
[sources] Highlight JSX in every file that looks like JavaScript.

This morally reverts https://crrev.com/c/4020557, and changes the code
highlighting logic to allow JSX constructs in all files that look like
JavaScript. The reason here is that in the React ecosystem, it's far too
common to use .js file extension than using the proper .jsx file
extension. Even the official React examples page[^1] points to examples
that use .js instead of .jsx, so we'd break a lot of users for no good
reason if we're strict here.

[^1]: https://reactjs.org/community/examples.html

Bug: chromium:1320204
Change-Id: I01b0c7a7667c604aeda7b98356669f94126966de
Fixed: chromium:1383863
Before: https://imgur.com/uKB1HS7.png
After: https://imgur.com/agHmr6P.png
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4020515
Auto-Submit: Benedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Jaroslav Sevcik <jarin@chromium.org>
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
2 files changed
tree: 130c15a3adc98a6ca912207427a9aba771365d25
  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. AUTHORS
  27. BUILD.gn
  28. codereview.settings
  29. DEPS
  30. LICENSE
  31. OWNERS
  32. package-lock.json
  33. package.json
  34. PRESUBMIT.py
  35. README.md
  36. tsconfig.json
  37. 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.

Project documentation

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.

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