perf: emit_assets only emit changed assets

[jerrykingxyz]

Related issue (if exists)

Before

After

Summary

🤖 Generated by Copilot at bb1ef0f

This pull request implements a feature that allows the compiler to only emit changed assets, except for the hot module replacement assets, which are always emitted. This can improve the performance and efficiency of the compilation process. To achieve this, the pull request adds a version field to the Asset and CompilationAsset structs, which stores the content hash of the asset. It also adds and implements a remove_file method to the AsyncFileSystem trait and its concrete implementations, which enables the compiler to delete outdated assets from the output directory. Additionally, it modifies the OutputOptions and DevtoolPlugin structs to set the version field of the asset info variables accordingly.

Walkthrough

🤖 Generated by Copilot at bb1ef0f

• Add a new feature that allows the compiler to only emit changed assets by comparing the content hash of the assets (link, link, link, link, link, link, link, link, link, link)
• Add a new method remove_file to the AsyncFileSystem trait and implement it for the NativeFileSystem and NodeFileSystem structs using the tokio::fs::remove_file and fs.unlinkSync functions respectively (link, link, link, link, link, link, link, link)
• Add a mut modifier and a default value assignment to the asset variable in the for loop in crates/rspack_core/src/compiler/hmr.rs to ensure that the hot module replacement assets are always emitted (link, link)

[faga295]

Hey @jerrykingxyz , I wonder how this graph in your description was generated, this look useful

[ahabhgk]

The general overview looks good to me, I like the version concept, good job 👍

[jerrykingxyz]

Hey @jerrykingxyz , I wonder how this graph in your description was generated, this look useful

@faga295 https://web-infra-dev.github.io/rspack-dev-guide/profiling/intro.html#chrome