react

mirror of https://github.com/zebrajr/react.git synced 2026-01-15 12:15:22 +00:00

Files

Jan Kassens afea1d0c53 [flow] make Flow suppressions explicit on the error (#26487 )

Added an explicit type to all $FlowFixMe suppressions to reduce
over-suppressions of new errors that might be caused on the same lines.

Also removes suppressions that aren't used (e.g. in a `@noflow` file as
they're purely misleading)

Test Plan:
yarn flow-ci

2023-03-27 13:43:04 +02:00

src

[flow] make Flow suppressions explicit on the error (#26487 )

2023-03-27 13:43:04 +02:00

e2e-regression.html

DevTools] e2e Regression Testing App (#24619 )

2022-05-26 11:36:00 -04:00

e2e.html

Refactored DevTools test shell for e2e (#22968 )

2021-12-15 11:42:59 -05:00

index.html

[DevTools] add perf regression test page in shell (#25078 )

2023-01-04 17:31:13 -05:00

multi.html

DevTools: Support mulitple DevTools instances per page (#22949 )

2021-12-14 12:16:16 -05:00

package.json

DevTools] e2e Regression Testing App (#24619 )

2022-05-26 11:36:00 -04:00

perf-regression.html

[DevTools] add perf regression test page in shell (#25078 )

2023-01-04 17:31:13 -05:00

README.md

Add details in READMEs for react-devtools local developement (#24148 )

2022-03-24 10:04:12 -04:00

webpack.config.js

[DevTools] add perf regression test page in shell (#25078 )

2023-01-04 17:31:13 -05:00

README.md

Harness for testing local changes to the react-devtools-inline and react-devtools-shared packages.

Development

This target should be run in parallel with the react-devtools-inline package. The first step then is to run that target following the instructions in the react-devtools-inline README's local development section.

The test harness can then be run as follows:

cd packages/react-devtools-shell

yarn start

Once you set both up, you can view the test harness with inlined devtools in browser at http://localhost:8080/