perf: enable the Node.js compile cache in the CLI entry point - #21523
Conversation
🦋 Changeset detectedLatest commit: d057a59 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
PR SummaryLow Risk Overview On Node.js 22.8+, it calls Reviewed by Cursor Bugbot for commit d057a59. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
This PR is packaged and the instant preview is available (929b113). Install it locally:
npm i -D webpack@https://pkg.pr.new/webpack@929b113
yarn add -D webpack@https://pkg.pr.new/webpack@929b113
pnpm add -D webpack@https://pkg.pr.new/webpack@929b113 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #21523 +/- ##
==========================================
- Coverage 93.79% 93.79% -0.01%
==========================================
Files 620 620
Lines 73798 73798
Branches 21306 21306
==========================================
- Hits 69220 69218 -2
- Misses 4578 4580 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Merging this PR will degrade performance by 26.27%
|
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Memory | benchmark "asset-modules-resource", scenario '{"name":"mode-development-rebuild","mode":"development","watch":true}' |
844.4 KB | 1,200.3 KB | -29.64% |
| ❌ | Memory | benchmark "devtool-eval", scenario '{"name":"mode-production","mode":"production"}' |
10.5 MB | 13.6 MB | -22.73% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing perf/enable-compile-cache (d057a59) with main (fbcbe3e)1
Footnotes
|
@bjohansebas lets make the same in webpack-cli, some developers uses webpack-cli, instead webpack directly |
Summary
What kind of change does this PR introduce?
Did you add tests for your changes?
Does this PR introduce a breaking change?
If relevant, what needs to be documented once your changes are merged or what have you already documented?
Use of AI