fix: ABSOLUTE_PATH_REGEXES should also accept forward slashes#20403
Open
CertainLach wants to merge 1 commit intowebpack:mainfrom
Open
fix: ABSOLUTE_PATH_REGEXES should also accept forward slashes#20403CertainLach wants to merge 1 commit intowebpack:mainfrom
CertainLach wants to merge 1 commit intowebpack:mainfrom
Conversation
Both forward and inverse slashes are valid on Windows
|
|
alexander-akait
requested changes
Feb 3, 2026
Member
alexander-akait
left a comment
There was a problem hiding this comment.
Please fix lint and add a test case
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.
Summary
Latest version of webpack warns when it sees paths like C:/Users/..., despite those paths being valid for windows.
What kind of change does this PR introduce?
Both forward and back slashes are valid on Windows, this patch makes this warning go away, those paths are not affected by the normalization step below.