mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-09-30 09:17:09 +08:00
Mathias Bynens
cdcfba01d1
Without this patch: ``` $ npm run check-json > chrome-devtools-frontend@ check-json ~/projects/devtools/devtools-frontend > node scripts/json_validator/validate_module_json.js schema id ignored http://json-schema.org/draft-04/schema# schema id ignored http://json-schema.org/draft-04/schema# ~/projects/devtools/devtools-frontend/node_modules/ajv/lib/ajv.js:92 if (!v) throw new Error('no schema with key or ref "' + schemaKeyRef + '"'); ^ Error: no schema with key or ref "http://json-schema.org/draft-04/schema#" at Ajv.validate (~/projects/devtools/devtools-frontend/node_modules/ajv/lib/ajv.js:92:19) at Ajv.validateSchema (~/projects/devtools/devtools-frontend/node_modules/ajv/lib/ajv.js:173:20) at Ajv._addSchema (~/projects/devtools/devtools-frontend/node_modules/ajv/lib/ajv.js:306:10) at Ajv.addSchema (~/projects/devtools/devtools-frontend/node_modules/ajv/lib/ajv.js:136:29) at Ajv.addMetaSchema (~/projects/devtools/devtools-frontend/node_modules/ajv/lib/ajv.js:151:8) at Object.<anonymous> (~/projects/devtools/devtools-frontend/scripts/json_validator/validate_module_json.js:20:5) at Module._compile (internal/modules/cjs/loader.js:776:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10) at Module.load (internal/modules/cjs/loader.js:643:32) at Function.Module._load (internal/modules/cjs/loader.js:556:12) ``` After applying this patch: ``` $ npm run check-json > chrome-devtools-frontend@ check-json ~/projects/devtools/devtools-frontend > node scripts/json_validator/validate_module_json.js schema $id ignored http://json-schema.org/draft-07/schema# schema $id ignored http://json-schema.org/draft-07/schema# schema $id ignored http://json-schema.org/draft-07/schema# ``` Fixed: chromium:1030215 Change-Id: Ie799ffbc9dfe50bdfedb18a0d9ac2ce63a9e4439 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/1953774 Auto-Submit: Mathias Bynens <mathias@chromium.org> Commit-Queue: Mathias Bynens <mathias@chromium.org> Reviewed-by: Tim van der Lippe <tvanderlippe@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
- jsdoc_validator - enforces the use of Closure type annotations
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
- optimize_svg_images.py - manually run when changing svg images
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).
Closure
DevTools manually rolls the closure compiler to ./closure. If you manually roll closure compiler, you will need to re-generate the closure_runner (in ./closure) and jsdoc_validator custom jars using the python scripts in their respective directory.