-
-
Notifications
You must be signed in to change notification settings - Fork 480
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Coordinated fix on Feb 12 broke Windows path handling between node-glob and minimatch #471
Comments
similar issue after
|
For right now, the only solution I can think of is to pin glob at 7.2.1, or 7.2.0 if 7.2.1 is the issue. |
@jsuddsjr Is this not an issue on 7.2.1? If so, how about 7.2.0? |
The issue seems to be at 73feafd. It will not show up on non-windows systems. allowWindowsEscape is documented here, which indicates that the translation from package.json "overrides": {
"glob": "7.2.0"
} |
This is a fix to isaacs#471, by a partial revert of 73feafd. See my comment on the issue (isaacs#471 (comment)) for more details.
7.2.0 is work. |
Could you try overriding glob to my PR and checking if it works? package.json "overrides": {
"glob": "github:nicolas377/node-glob#revert-allowWindowsEscape"
} |
It is work.
|
7.2.1 introduced the flag, 7.2.0 works as expected. |
Can you try using glob 7.2.3? If that doesn't work, idk, might just have to roll back that change entirely, or do a different thing. |
The only problem was setting that config option to true, the upgrade didn't break anything. 7.2.3 should be working. If it is, I'll go ahead and close my PR. |
Great, 7.2.3 is work. |
When using
allowWindowsEscape=true
in minimatch options, glob is forcing minimatch to treat the path as though it contained escapes rather than Windows path separators (backslashes). Notice the negation in the following statement, which would entirely fix the issue if it were allowed to run.Therefore,
[email protected]
combined withminimatch@^3.1.1
cannot locate files using patterns like:Unfortunately, this is causing the latest version of Storybook to fail to locate configuration files in its default state in Windows. Error: No configuration files have been found in your configDir.
Please coordinate another fix.
The text was updated successfully, but these errors were encountered: