[Bug]: persistent cache lead to incremental build failed with @rspress/plugin-preview

[liuwenzhuang]

Version

System:
    OS: Linux 5.15 Ubuntu 24.04.2 LTS 24.04.2 LTS (Noble Numbat)
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
    Memory: 1.52 GB / 9.72 GB
    Container: Yes
    Shell: 5.2.21 - /bin/bash
  npmPackages:
    @rspress/core: 2.0.0-beta.31 => 2.0.0-beta.31 
    @rspress/plugin-preview: 2.0.0-beta.31 => 2.0.0-beta.31

Details

Before every build, the temp dir(node_modules/.rspress/ default) will be delete, and the @rspress/plugin-preview should generate components in node_modules/.rspress/virtual-demo/. Howerver, the persistent cache lead @rspress/plugin-preview not regenerate components in node_modules/.rspress/virtual-demo/, the incremental build will throw error like:

 × Module not found: Can't resolve 'XX/node_modules/.rspress/virtual-demo/_market_index_1.tsx' in 'XX/docs/market'

Reproduce link

https://codesandbox.io/p/devbox/plugin-preview-not-rerender-jxvk3m

Reproduce Steps

1. run npm run build
2. run npm run build again

[liuwenzhuang]

Persistent cache use routeService.generateRoutesCode() as an item of cacheDigest, but it only reflects route components and md(x) file paths, not considering the file content. In other words, if you just change the content of md(x) files, the existing persistent cache will still be considered valid.

[SoonIter]

Investigation: Some virtual modules are cached and not recorded in the buildDependencies of the cache.

Solutions: plugin-preview and plugin-playground should be refactored with rsbuild-plugin-virtual-module and not make virtual modules separatedly