Passing nocase: true on Windows causes no matches about glob-stream HOT 11 CLOSED

Need the version of glob you are using directly. If it is latest, that is quite different

from glob-stream.

I had just done an npm install glob for testing, which installed [email protected]. Looking at [email protected], I also just installed [email protected] (per https://github.com/gulpjs/glob-stream/blob/v5.0.0/package.json), and get the same results.

from glob-stream.

@bdukes cool. Can you also test glob using the on('match') syntax to see if it is a bug with that?

from glob-stream.

@bdukes ref https://github.com/isaacs/node-glob#events

from glob-stream.

[email protected] works fine using on('match')

from glob-stream.

@bdukes can you please create a repo for reproduction that includes files and scripts? I have some time to look at this today

from glob-stream.

I've put a repro at https://dl.dropboxusercontent.com/u/5536031/glob-stream-nocase-repro.zip

from glob-stream.

Thanks! It seems this is only happening on window's and is related to us making the glob absolute. I think I will be able to track this into the glob library

from glob-stream.

👍

from glob-stream.

The example below has the same problem as described. Looks to be a node-glob issue.

var testGlob = new glob.Glob('C:\\Users\\phated\\Downloads\\glob-stream-nocase-repro\\testing\\**\\*.glob', { nocase: true });
testGlob.on('match', function (match) {
    console.log('glob matched', match);
}).on('end', function () {
    console.log('done matching via glob');
})

from glob-stream.

Found the issue already opened for this over on glob: isaacs/node-glob#123

Going to close this as the bug is happening upstream and there isn't much we can do about it. You could probably poke some of the related threads. There seems to be a PR open that tries to solve it but is way out of date.

from glob-stream.