Commit c340e29
committed
build: prune stale bundle chunks before rebuilding dists
Stale content-hashed chunks from earlier builds accumulate in dist/ and
carry old schema-fence values; anyone verifying a rebuild by grepping
dist/*.js finds a mix of old and new fences and reaches the wrong
conclusion (tonight's fleet seat-death postmortem). Deleting the bundle
entrypoints and hashed chunks before bun build makes the on-disk chunk
set exactly the referenced set, so an artifact grep is trustworthy.
Declaration trees and the compiled TUI are untouched.1 parent e4a49ff commit c340e29
2 files changed
Lines changed: 2 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
26 | 26 | | |
27 | 27 | | |
28 | 28 | | |
29 | | - | |
| 29 | + | |
30 | 30 | | |
31 | 31 | | |
32 | 32 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
30 | 30 | | |
31 | 31 | | |
32 | 32 | | |
33 | | - | |
| 33 | + | |
34 | 34 | | |
35 | 35 | | |
36 | 36 | | |
| |||
0 commit comments