Add workaround for windows x yarn users #93
Merged
Conversation
This file contains 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
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/vercel/turbo-site/r3uV6CNpVjvKYeGnM34KHxSJDT2m |
sokra
added a commit
that referenced
this pull request
Oct 25, 2022
Follow sourceMappingURL references
sokra
pushed a commit
that referenced
this pull request
Oct 25, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
path.Jointofilepath.Joineverywhere (TIL / yeesh)yarn.lockon Windows machines so this falls back to full lockfile hashing (w/yarn) (like npm and pnpm). This will mean windows x yarn users will have different hashes than unix x yarn users, but this at least moves us from p0 to p1 problem.git.ChangedFiles#techdebt