results are in reverse alphabetical order about node-glob HOT 5 CLOSED

That's good to know! They do seem to consistently be in reverse order though, for the cases I've tried. Do you think there's something that got changed recently that caused that? I'll make sure to add a .sort() wherever I'm accidentally depending on it, but I imagine there are others who will find the reverse order unexpected and might hit issues.

Failing that, would you accept a docs update pull request?

from node-glob.

They're not sorted at all, and the order is non deterministic, set by os latency. Do not depend on it.

from node-glob.

Version 9 removed sorting. To sort results just as version 8 did, use:

glob.sync(...).sort((a, b)=> a.localeCompare(b, 'en'))

from node-glob.

They do seem to consistently be in reverse order though, for the cases I've tried.

That is 100% a result of how your computer's file system chooses to return results. On a different operating system, file system, disk controller, ..., it could easily be returned in alphabetical order, in order of last access, entirely random, or any other arbitrary order.

Sort if you depend on it, don't depend on it if you're not sorting it yourself.

from node-glob.

And yes, doc patch welcome 🤗

from node-glob.