fix(build): cache key should consider file path

[fi3ework]

fix #947

[brc-dd]

IMO just setting cacheKey to this would work:

const cacheKey = cache.get(JSON.stringify({ src, file }))

There is no need for complex functions as src and file are strings and their order will always be same if the code is written like this. So stringifying {src, file} should yield same result every time if the content is unchanged.

[brc-dd]

I have a doubt too. What would be the need of caching then? file cannot be same for two files. Will there ever be a hit?

[fi3ework]

I though node.js's JSON. stringify was not stable, but it does. So yes, we do not need the hash function anymore.

[fi3ework]

I have a doubt too. What would be the need of caching then? file cannot be same for two files. Will there ever be a hit?

AFAIK, the cache will be hit in handleHotUpdate stage if you're modifying the content the same as some cached content.

[brc-dd]

AFAIK, the cache will be hit in handleHotUpdate stage if you're modifying the content the same as some cached content.

Okay, I tested with debug, every markdown file is rendered twice during build, so setting cache reduces nearly half the time. It is still being triggered. And in dev server, a cache hit occurs if you change some content, save it, then undo the changes and then save it.

[brc-dd]

Thanks for the PR!