⚠️ No Changeset found

Latest commit: e50a89d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

This PR is packaged and the instant preview is available (a475512).

Install it locally:

• npm

npm i -D webpack@https://pkg.pr.new/webpack@a475512

• yarn

yarn add -D webpack@https://pkg.pr.new/webpack@a475512

• pnpm

pnpm add -D webpack@https://pkg.pr.new/webpack@a475512

Merging this PR will improve performance by ×2.4

⚡ 4 improved benchmarks
✅ 140 untouched benchmarks

Performance Changes

_{Comparing snapshot-per-case (e50a89d) with main (72a7ef3)}

Types Coverage

Looks good, just interesting maybe we can merge ConfigCacheTest.snap and ConfigTest.snap together, because they should be the same, it is just a cache testing so output should be the same always (only for these tests)

We run ConfigCacheTest and ConfigTest in parallel as separate workflow tasks, i just concern about the race condition where either ConfigTest writes its snapshot before ConfigCacheTest, or ConfigCacheTest writes first, and it will lead to different snapshot content.

@hai-x thanks for this refactor