fix(css): reset render cache on renderStart #14326
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fix unocss fail in ecosystem-ci, since #13974 that revealed a bug in our code.
Additional context
Unocss has a test in lib mode with multiple outputs, each output is rendered once. The
css-post
plugin has caches for the render hooks, e.g.renderChunk
andgenerateBundle
, the caches are scoped to each render (aka each output).However, we reset our cache in
buildStart
, that means each render share the same cache, which is incorrect. This PR changes torenderStart
instead.What is the purpose of this pull request?
Before submitting the PR, please make sure you do the following
fixes #123
).