mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-07 04:26:32 +08:00
Tim van der Lippe
28af9fbe78
This reverts commitaaae6b021a. Reason for revert: always check if tsconfig.json needs to be updated Original change's description: > Revert "Do not overwrite generated files when contents remains the same" > > This reverts commitc1e414725a. > > Reason for revert: Seems to be the cause for CQ compilation errors: > https://ci.chromium.org/ui/p/devtools-frontend/builders/try/devtools_frontend_linux_blink_light_rel/19852/overview > > Original change's description: > > Do not overwrite generated files when contents remains the same > > > > To ensure that build timestamps don't unnecessarily cause full rebuilds, > > make sure that we only write the generated contents to a file (if it > > exists already) if it would be the same. This ensures that the file > > timestamps remain the same, which will lead GN to conclude that the > > build action is a noop (which it is). > > > > On a new year, the file contents would actually be different, so it > > would cause a proper rebuild. However, in all months between when the > > timestamp changes, it won't cause is unnecessarily to rebuild all these > > files, even though the year hasn't changed (but the timestamp it was > > based on did). > > > > R=jacktfranklin@chromium.org > > > > Bug: 1283883 > > Change-Id: I2bdc3a79de710236c1501b21fa505692336cfa82 > > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3377942 > > Auto-Submit: Tim Van der Lippe <tvanderlippe@chromium.org> > > Reviewed-by: Jack Franklin <jacktfranklin@chromium.org> > > Commit-Queue: Tim Van der Lippe <tvanderlippe@chromium.org> > > Bug: 1283883 > Change-Id: I938cfe20a7ecf6df6c7becc9fa73a3dcfebe457c > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3380583 > Auto-Submit: Simon Zünd <szuend@chromium.org> > Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> > Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bug: 1283883 Change-Id: Iae23d721bdeb4c8af227903a38255ee9fc1bc49d Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3386675 Commit-Queue: Tim Van der Lippe <tvanderlippe@chromium.org> Reviewed-by: Jack Franklin <jacktfranklin@chromium.org>
DevTools Scripts
Development workflow scripts
These are scripts that can be useful to run independently as you're working on Chrome DevTools front-end.
The newer scripts such as for testing and hosted mode are written in Node.js, which has become the standard toolchain for web apps. The older scripts such as building (e.g. bundling and minifying) are written in Python, which has first-class support in Chromium's infrastructure.
Overview
Folders
- build - Python package for generating DevTools debug and release mode
- chrome_debug_launcher - automagically finds Chrome Canary and launches it with debugging flags (e.g. remote debugging port)
- closure - see section on Closure Compiler below
- gulp - experimental build process written in node.js & gulp to remove the dependency on Chromium-specific build tools (i.e. gn and ninja)
- hosted_mode - run DevTools on a localhost development server
Python Scripts
- compile_frontend.py - runs closure compiler to do static type analysis
- Note: the compiled outputs are not actually used to run DevTools
- lint_javascript.py - run eslint
Node.js scripts
The easiest way to run the node.js scripts is to use npm run which displays all the commands. For more information on the specific npm run commands, take a look at the primary devtools front-end readme (../readme.md).