fix: use POSIX paths with glob 8 on Windows #66
Merged
Conversation
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
BREAKING CHANGE: Use Jest v28
3 tasks
MichaelDeBoey
force-pushed
the
update-dependencies
branch
from
588fd87 to
4f80ef3
Compare
Owner
|
@nickmccurdy Could you please rebase your branch & fix conflicts? |
MichaelDeBoey
force-pushed
the
update-dependencies
branch
from
4f80ef3 to
6ca2f16
Compare
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.
What: use POSIX paths with glob 8 on Windows
Why: glob 8 requires using POSIX paths, even on Windows
How: only use POSIX paths (instead of Windows paths) when using
globBreaking change: Backslashes are interpreted as literal escapes, not path separators, on Windows
Checklist: