what i cant understand is build.rollupOptions.cache means like production env build cache? but when i open that ，i cant perceive anything changed

[yfools]

Documentation is

• Missing
• Outdated
• Confusing
• Not sure?

Explain in Detail

well,the cache option seems used to production build cache, but i cant achieve that purpose

my .cache or .vite file have not anything changed,and the build speed is same as previous

Your Suggestion for Changes

Perhaps someone can answer my confusion? thanks

Reproduction

No response

Steps to reproduce

No response

[bluwy]

Using the Rollup cache would also need Vite to handle writing the cache to the filesystem in order to be effective. Specifically, bundle.cache here:

vite/packages/vite/src/node/build.ts

Line 756 in 61357f6

bundle = await rollup(rollupOptions)

However, instead of implementing it in Vite, I went with a different approach at #11454 instead as I found enabling cache might not always lead to faster builds. The problem is that the cache saves a ton of module information in memory (specifically the AST), and this information is kept in the memory until the bundling ends. The amount of memory that piles up will slow down building too.

When Vite disables it, the information can be dropped immediately whenever its garbage collected instead, so there's less memory pressure when building, leading to faster builds. While Rollup's cache can technically improve subsequent builds, I found that in most cases due to the memory pressure, it's hard to finish the first build in the first place.