Skip to content

fix: Content-hash-based filename when bundling with wasm_split#5340

Open
SuperKenVery wants to merge 1 commit intoDioxusLabs:mainfrom
SuperKenVery:fix/hash-filename-when-wasm-split
Open

fix: Content-hash-based filename when bundling with wasm_split#5340
SuperKenVery wants to merge 1 commit intoDioxusLabs:mainfrom
SuperKenVery:fix/hash-filename-when-wasm-split

Conversation

@SuperKenVery
Copy link

@SuperKenVery SuperKenVery commented Mar 1, 2026

Add content hash to asset filenames. Without this, client may continue to use cached old versions even if the server has been updated.


I tried directly removing the self.wasm_split check. Seems working well.

Closes #5339

@SuperKenVery SuperKenVery requested a review from a team as a code owner March 1, 2026 16:46
@chtpl
Copy link

chtpl commented Mar 2, 2026

could you please add an explanation to the body of the commit message why this is done?

My assumption is that it helps with caching?

@SuperKenVery
Copy link
Author

SuperKenVery commented Mar 2, 2026

Yes exactly, this fixes caching. Without this, clients will use old html or wasm files even if server has updated.


I added description to PR body. Adding to commit body would require force push, tell me if you want that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Content hash based filename is disabled when --wasm-split is present

2 participants