Skip to content

Conversation

eps1lon
Copy link
Collaborator

@eps1lon eps1lon commented Sep 10, 2025

Previous version relied on having built something before. These changes make the script work on a fresh clone/worktree. Technically you do need to run yarn build react-debug-tools react-refresh internal-test-utils because we're not actually doing regression tests for those packages but that's an issue for the tests using those package. The other tests should be able to run on a clean worktree.

This is also fixing a bug where we were using the built react-is not the published one.

Test plan

node ./scripts/ci/download_devtools_regression_build.js 16.0 --replaceBuild on

  • only a fresh worktree
  • repeatedly

@meta-cla meta-cla bot added the CLA Signed label Sep 10, 2025
@github-actions github-actions bot added the React Core Team Opened by a member of the React Core Team label Sep 10, 2025
@react-sizebot
Copy link

react-sizebot commented Sep 10, 2025

Comparing: 288d428...a82f923

Critical size changes

Includes critical production bundles, as well as any change greater than 2%:

Name +/- Base Current +/- gzip Base gzip Current gzip
oss-stable/react-dom/cjs/react-dom.production.js = 6.68 kB 6.68 kB = 1.83 kB 1.83 kB
oss-stable/react-dom/cjs/react-dom-client.production.js = 530.65 kB 530.65 kB = 93.49 kB 93.49 kB
oss-experimental/react-dom/cjs/react-dom.production.js = 6.69 kB 6.69 kB = 1.83 kB 1.83 kB
oss-experimental/react-dom/cjs/react-dom-client.production.js = 658.20 kB 658.12 kB = 115.79 kB 115.77 kB
facebook-www/ReactDOM-prod.classic.js = 682.36 kB 682.25 kB = 119.83 kB 119.80 kB
facebook-www/ReactDOM-prod.modern.js = 672.79 kB 672.68 kB = 118.14 kB 118.11 kB

Significant size changes

Includes any change greater than 0.2%:

(No significant changes)

Generated by 🚫 dangerJS against a82f923

}
await downloadRegressionBuild();
} catch (e) {
console.log(chalk.red(e));
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I found it annoying that this script always exited with a zero exit code. This could make CI fail but I suspect we'd want to know about these failures. I'm actively working on fixing the regression test suite so I'll notice if this reveals some other issue.

@eps1lon eps1lon changed the title Allow running download_devtools_regression_build.js on clean repo Allow running download_devtools_regression_build.js on a clean repo Sep 10, 2025
@eps1lon eps1lon marked this pull request as ready for review September 10, 2025 13:52
@eps1lon eps1lon requested a review from hoxyq September 10, 2025 13:52
@eps1lon eps1lon requested a review from hoxyq September 11, 2025 16:55
@eps1lon eps1lon merged commit 47664de into facebook:main Sep 13, 2025
241 checks passed
@eps1lon eps1lon deleted the sebbie/09-10-allow_running_download_devtools_regression_build.js_on_clean_repo branch September 13, 2025 09:07
github-actions bot pushed a commit to code/lib-react that referenced this pull request Sep 14, 2025
github-actions bot pushed a commit to muditbhadouria/react that referenced this pull request Sep 14, 2025
github-actions bot pushed a commit to muditbhadouria/react that referenced this pull request Sep 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed React Core Team Opened by a member of the React Core Team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants