You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7fae777
Browse filesBrowse the repository at this point in the historyBrowse files
fix(analyzable): repair hashed names on demand instead of keeping the runtime form
A baked reference into a chunk whose hashed name has nothing repairing
it kept the runtime form unless the fold could settle it first — which
a pair naming each other, a [chunkhash] name in a cycle, or a two-depth
stand-in into content-named chunks all defeat. Such a stand-in is now
reserved with a repair mark: the deferred fill records it, and
RealContentHashPlugin runs for those builds alone where
optimization.realContentHash did not ask for it, tracking [chunkhash]
values as well so a name the fill left stale is re-hashed from what it
left. The fold stays the cheap first choice wherever it applies.
With every hashed name repairable, a chunk that could not be named no
longer exists, so the partial url maps and the per-asset runtime
fallback behind them go, as do the deferral bailouts and the
reachability walk that only served their messages.
0 commit comments