fix: use relative paths in _metadata.json#7299
Merged
Conversation
bluwy
reviewed
Mar 13, 2022
bluwy
approved these changes
Mar 13, 2022
This was referenced Mar 14, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
We currently use absolute paths in
_metadata.jsonin the pre-bundled deps dir, this means that if the user moves or copy a Vite app folder, the cache will end up in an invalid state.I think users may be getting hard to report bugs because of this. We could make the paths relative to the deps dir (where the
_metadata.jsonis located) to avoid this issue.What is the purpose of this pull request?