Fix for Windows Git Bash w/ pnpm #116
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
0x80
approved these changes
Dec 14, 2024
0x80
requested changes
Dec 14, 2024
|
lint & lint:format are now passing |
0x80
approved these changes
Dec 17, 2024
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.
I want to say upfront that this tool is fantastic, and so is the typescript mono repo example. I was able to finally restructure my mono-repo the way I've been hoping to and remove all my home-grown firebase publishing hacks.
This PR addresses problems I had with "packages/common" in a Windows git bash environment using pnpm. Naturally, both changes have to do with forward vs back slashes.