OSSForks/react
1
0
Fork 0
mirror of https://github.com/zebrajr/react.git synced 2025-12-06 00:20:04 +01:00
Code Issues Actions 5 Packages Projects Releases Wiki Activity
main
react/fixtures/devtools/scheduling-profiler
History
Sebastian Markbåge db5e6250d4
Rename yarn build-combined to just yarn build (#26192) 
It's confusing to new contributors, and me, that you're supposed to use
`yarn build-combined` for almost everything but not fixtures.

We should use only one build command for everything.

Updated fixtures to use the folder convention of build-combined.
2023-02-17 16:00:18 -05:00
..
.gitignore Added test fixture for scheduling profiler (#21397) 2021-04-30 15:23:45 -04:00
app.js Remove unstable_createRoot from internal builds (#21698) 2021-06-17 11:29:30 -07:00
index.html Added test fixture for scheduling profiler (#21397) 2021-04-30 15:23:45 -04:00
README.md Added test fixture for scheduling profiler (#21397) 2021-04-30 15:23:45 -04:00
run.js Rename yarn build-combined to just yarn build (#26192) 2023-02-17 16:00:18 -05:00

README.md

Test fixture for packages/react-devtools-scheduling-profiler

  1. First, run the fixture:
# In the root directory
# Download the latest *experimental* React build
scripts/release/download-experimental-build.js

# Run this fixtures
fixtures/devtools/scheduling-profiler/run.js
  1. Then open localhost:8000/ and use the Performance tab in Chrome to reload-and-profile.
  2. Now stop profiling and export JSON.
  3. Lastly, open react-scheduling-profiler.vercel.app and upload the performance JSON data you just recorded.