mirror of https://github.com/react/react-native-devtools-frontend.git synced 2026-10-07 20:39:31 +08:00

Files

T

Jack Franklin e60446000d Lint for checkbox stylesheet adoption in Lit components

This CL introduces (but does not enable) an ESLint rule to check that if
a Lit component renders a checkbox, that it also imports and adopts the
common `Input.checkboxStyles` into the component's shadow root.

We can also roll this rule out to the text inputs too, but I wanted to
start with just one and see how it goes. I will follow up this CL with a
CL to enable this rule.

Bug: 1316297
Change-Id: Ibed7109d5948c8be3f4c9d376738290137e444ff
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3586906
Reviewed-by: Johan Bay <jobay@chromium.org>
Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
Auto-Submit: Jack Franklin <jacktfranklin@chromium.org>

2022-04-19 08:53:26 +00:00

build

Run build scripts with vpython3

2022-02-25 10:12:14 +00:00

component_server

Fix paths not using sharedResourcesBase in component-server

2022-01-05 13:07:57 +00:00

deps

Update @typescript-eslint/plugin to 5.20.0

2022-04-19 07:12:14 +00:00

eslint_rules

Lint for checkbox stylesheet adoption in Lit components

2022-04-19 08:53:26 +00:00

hosted_mode

[e2e] Load DevTools on a different origin than the target page

2022-02-16 12:43:57 +00:00

javascript_natives

Update roll_deps.py to also run javascript_natives/ script

2022-02-02 18:18:51 +00:00

migration/class-fields

Update migration script for private class methods

2021-12-15 12:16:27 +00:00

protocol_typescript

replace protocol.d.ts with protocol.ts

2022-01-24 01:35:02 +00:00

stylelint_rules

Updated no-multiple-empty-lines to only have 1 as max

2021-07-28 14:10:15 +00:00

test

Migrate to py3

2022-03-15 13:19:16 +00:00

__init__.py

The Great Blink mv for source files, part 2.

2018-04-07 15:32:37 +00:00

.eslintrc.js

Fix issues discovered by ESLint 7

2020-11-13 12:15:35 +00:00

check_experiments.js

Allow removal of entries from UMA enums

2021-12-21 08:42:54 +00:00

check_external_links.js

Introduce new script to check external links

2021-02-01 08:33:44 +00:00

devtools_paths.js

use __dirname

2022-02-07 12:18:16 +00:00

devtools_paths.py

typescript: introduce devtools_skip_typecheck build flag

2022-01-24 02:19:51 +00:00

npm_test.js

Rename arg name --time-out-ms for rwt

2022-02-14 17:15:27 +00:00

OWNERS

Remove outdated owner in scripts/

2021-05-04 11:10:07 +00:00

README.md

Dynamically optimize svgs

2021-06-10 10:09:30 +00:00

tsconfig.json

Component bridges generation

2020-03-26 11:36:00 +00:00

utils.js

Run ESLint on the scripts directory

2020-03-11 14:47:51 +00:00

watch_build.js

Use chokidar as the file watcher

2021-07-15 16:12:46 +00:00

whitespaces.txt

Whitespace to trigger builders

2022-01-26 14:24:02 +00:00

README.md

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).