fix(hmr): fix HMR failure for @include markdown files due to cache key mis

[yyznm]

Description

Issue where HMR doesn't occur when markdown files included via @include are modified, caused by the route rewriting feature.

This is the minimal reproducible code for the bug.

This is the normal behavior

success.mp4

After adding the rewrites configuration, it's found that updates don't work as expected

error.mp4

The root cause of this issue is that the relativePath used to generate the cacheKey is the rewritten path:

// src/node/markdownToVue.ts
file = rewrites.get(file) || file
const relativePath = slash(path.relative(srcDir, file))
const cacheKey = JSON.stringify({ src, ts, relativePath })
if (options.cache !== false) {
  const cached = cache.get(cacheKey)
  if (cached) {
    debug(`[cache hit] ${relativePath}`)
    return cached
  }
}
// ...

However, the only place where clearCache is called with parameters is in plugin.ts, where the relativePath here is the original path before rewriting. This prevents the cache from being cleared properly, resulting in consistent hits to the cached content and thus failing to update to the new content:

// src/node/plugin.ts
importerMap[slash(file)]?.forEach((relativePath) => {
  clearCache(relativePath)
  // ...
})
// ...

My solution is to use the original path when generating the cacheKey.

Linked Issues

Additional Context