fix: revert #5601 #6025, don't resolve rollupOptions.input #6680
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 #6576
In [email protected] we merged #5601 resolving the paths in
rollupOptions.input
. This was done to fix path issues in Windows that are not clear enough from the issue. See unocss/unocss#88 (the issue there no longer seems relevant to unocss as the playground no longer usesrollupOptions.input
in its vite config)The added resolve was the basic one we use for lib mode entry, and doesn't take into account virtual paths or paths to dependencies that are valid inputs in rollup. See for example https://rollupjs.org/guide/en/#a-simple-example
This PR adds a basic test case in one of the playgrounds, and reverts the change. We should do this in a minor in case someone in the ecosystem started to rely on the new resolved config.
Would you help us review and test this PR @sibbng @IanVS @ydcjeff @matthewp?
What is the purpose of this pull request?