Files
fkysly 1391ada12a build: strip the builder's absolute path from the published client artifact (#121)
client/client.js is committed AND published, so it must be byte-identical
regardless of whose machine built it. tsdown names the CSS module's
virtual chunk by absolute path, so the builder's checkout leaked into a
region comment: main currently ships /Users/<me>/work/dsh-market/… to
npm, and #99 arrived carrying D:\Github\… — every contributor's artifact
diff churned on the path plus every hashed class name.

normalize-client-banner now rewrites those virtual ids to a stable
repo-relative form (Windows separators included, so a Windows build
produces the same bytes) and fails the build if this builder's checkout
path survives anywhere else. The scan is deliberately narrow: the bundle
legitimately contains strings like 's:\' inside regexes, and a generic
drive-letter check would false-positive.

Spotted by @5102a while reviewing artifact diffs across PRs.
2026-08-16 22:56:19 +08:00
..