Skip to content

ryanto/rolldown-hash-issue

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Run with: node build.js

I would expect these two builds to have the same content hashes, since the content is unchanged. However, since rolldown runtime gets a new content hash, all files change.

build-1-output files:

chunk-react-BIXjCxC_.js
chunk-rolldown-runtime-B4Ym4T5x.js
entries-a-DHk7QRAg.js
entries-b-BRC5A8tn.js

build-2-output files:

chunk-react-6v51whlJ.js
chunk-rolldown-runtime-BDQlAIcz.js
entries-a-u7l8DAkT.js
entries-b-OYD0-tjf.js
entries-c-8xa5HYwO.js

The two chunk-rolldown-runtime files are byte-for-byte identical even though their filename hashes are different.

Command: shasum -a 256 build-1-output/chunk-rolldown-runtime-B4Ym4T5x.js build-2-output/chunk-rolldown-runtime-BDQlAIcz.js

Output:

8857aad4f904253f9a8bb160ae7ca249376498df7c3510b0cd92b4e5a2c3b6cb  build-1-output/chunk-rolldown-runtime-B4Ym4T5x.js
8857aad4f904253f9a8bb160ae7ca249376498df7c3510b0cd92b4e5a2c3b6cb  build-2-output/chunk-rolldown-runtime-BDQlAIcz.js

Command: wc -c build-1-output/chunk-rolldown-runtime-B4Ym4T5x.js build-2-output/chunk-rolldown-runtime-BDQlAIcz.js

Output:

192 build-1-output/chunk-rolldown-runtime-B4Ym4T5x.js
192 build-2-output/chunk-rolldown-runtime-BDQlAIcz.js

Command: cmp -l build-1-output/chunk-rolldown-runtime-B4Ym4T5x.js build-2-output/chunk-rolldown-runtime-BDQlAIcz.js

Output:

no output

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors