Skip to content

Commit e25f387

Browse files
justin808claude
andcommitted
fix: clarify webpack override comment — update upper bound, don't remove
The <5.106.0 range excludes all 5.106.x versions, so when a patched webpack ships the override upper bound needs updating, not removing. Also note that pnpm install is required to regenerate the lockfile. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
1 parent 928a483 commit e25f387

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -126,7 +126,7 @@
126126
"ajv overrides were intentionally excluded: ajv v8 breaks webpack's schema-utils/ajv-keywords.",
127127
"The 2 moderate ajv alerts (ReDoS in $data option) are tolerable — ajv only validates our own config files.",
128128
"webpack: 5.106.0 breaks ExecJS SSR (anonymous default export codegen bug).",
129-
"Upstream fix: webpack/webpack#20796 — remove webpack override once a patched version ships."
129+
"Upstream fix: webpack/webpack#20796 — update override upper bound once a patched webpack ships, then run pnpm install to regenerate the lockfile."
130130
],
131131
"overrides": {
132132
"react": "$react",

0 commit comments

Comments
 (0)