Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve benchmark setup, consistently rely on publishConfig #1648

Merged
merged 2 commits into from
Nov 3, 2024
Merged

Improve benchmark setup, consistently rely on publishConfig #1648

merged 2 commits into from
Nov 3, 2024

Commits on Nov 3, 2024

  1. Improve benchmark setup and rely on publishConfig 

    This commit has two related changes:

1. Clean up and document recent changes in the benchmark script. One of
   these changes is replacing ad-hoc rewrites of `package.json` files
   with a firm reliance on the `publishConfig` field, which should be
   reliable (since that's what we use when actually publishing).
2. Update all of the `package.json` files for published packages to have
   consistent `publishConfig` fields. This change also removed a bunch
   of historical cruft from the `package.json` files, which helped us
   to support environments during the ecosystem transition to
   package.json `exports` fields.
    @wycats
    wycats committed Nov 3, 2024
    Configuration menu
    Copy the full SHA
    406e17d View commit details
    Browse the repository at this point in the history

  2. Rely on git rev-parse to get the refs for perf

    @wycats
    wycats committed Nov 3, 2024
    Configuration menu
    Copy the full SHA
    dde2390 View commit details
    Browse the repository at this point in the history