vite: Assets with the same content are de-duplicated at build time

@hemengke1997 Yes I understand the difference. But we didn’t understand why you need to avoid the dedupe of the actual file. Would you provide more context about that?

I am trying to cache packed results. Because my project structure is multi-page, and each page is not directly related, the speed will be slower every time it is fully bundled, so I need know whether the file needs to be removed from the cache by controlling the hash. And multi-asset merging will cause cache instability. My need is very rare, so I don’t think there is any need to modify the vite source code. At first I thought it was a vite bundle bug. But I now think merging assets is reasonable for the vast majority of projects. Thank you for your enthusiasm and responsibility

@hemengke1997 Yes I understand the difference. But we didn’t understand why you need to avoid the dedupe of the actual file. Would you provide more context about that?

I’ve just checked with

• feat: include duplicate assets in the manifest #9928

this PR successfully resolves our issue with the same content in different files also.

Thank you guys!

We decided today that there isn’t a good use case yet to justify an option to avoid deduplication. Would you check if @timacdonald’s PR is enough for your needs:

• https://github.com/vitejs/vite/pull/9928

If not, please provide more context about the particular use case. Thanks!

@dostrog it is my personal opinion that although your issue is related, it is a unique issue.

Thanks for your reply! Yeah unique and rare, but exists.

at the moment I’ve just add file name + generate hash (unfortunately. do not have time for full PR) and use forked repo for Vite

in asset.ts:

...
    const map = assetHashToFilenameMap.get(config)!
    const contentHash = getHash(content + file) // <- make hash more unique
    const { search, hash } = parseUrl(id)
...

Sorry, my bad. I thought this issue was unnecessary. I’m very sorry.