Skip to content
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

Nested glob expander doesn't work across platforms #364

Closed
h2non opened this issue Dec 18, 2015 · 2 comments

Comments

@h2non
Copy link

commented Dec 18, 2015

The following glob patterns doesn't work as expected in OSX and Linux:

standard lib/**/*.js test/**/*.js

Expected to the processed:

lib/index.js
lib/folder/index.js
lib/folder/subfolder/index.js

However, it's only processed:

lib/folder/index.js
lib/folder/subfolder/index.js

I've been forced to fix it passing the following params:

standard lib/*.js lib/**/*.js test/*.js test/**/*.js

I realized that in Windows the glob patterns behaves properly, which is a bit disquieting.
Perhaps might be an issue of deglob package.

I'm running the latest version of standard.

@h2non h2non changed the title Nested glob expander doesn't work consistently across platforms Nested glob expander doesn't work across platforms Dec 18, 2015

@rstacruz

This comment has been minimized.

Copy link
Member

commented Dec 18, 2015

It might be an issue in your shell. /*/ is not supported in bash.

On Friday, December 18, 2015, Tomás Aparicio notifications@github.com
wrote:

The following glob patterns doesn't work as expected in OSX (not tested in
Linux):

standard lib//*.js test//*.js

Expected to the processed:

lib/index.js
lib/folder/index.js
lib/folder/subfolder/index.js

However, it's only processed:

lib/folder/index.js
lib/folder/subfolder/index.js

I've been forced to fix it passing the following params:

standard lib/.js lib/__/.js test/.js test/__/.js

I realized that in Windows the glob patterns behaves properly, which is a
bit disquieting.
Perhaps might be an issue of deglob package.


Reply to this email directly or view it on GitHub
#364.

@h2non

This comment has been minimized.

Copy link
Author

commented Dec 18, 2015

@rstacruz You're right, after wrapping it with quotes, it works. I'm running it from npm scripts, and I've assume that the arguments are properly passed to the shell binary.

@h2non h2non closed this Dec 18, 2015

@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
2 participants
You can’t perform that action at this time.