Sort Files with 'glob.sync'

[devalbm]

I have some problems to sort the files. Glob.sync order the files alphabetically. Is there any solution to order my way?

   /app
     |__ app.js
     |__ main.js

I have:
glob.sync("./app/*(main|app).js")

I want to include 'main.js' first and later 'app.js', but actually, sync does the opposite. The first file that "match" is app.js due to the alphabetical order.
Any Solution?
Thanks in advance.

[tarwich]

If at all possible, I would expect glob to return files in the order specified in patterns. This is the way that *nix glob works, and I use it for precedence.

Edit: It doesn't work this way. I'm not trying to answer OP, but rather agreeing. I'm currently working on a precedence filter for the results in my project -- I'm not sure how to fix it in this library.

[romellem]

FYI, just to add some more detail here, the docs show that the matches are sorted unless the nosort flag is set.

The code for this is in common.js, in the finish function.

[tarwich]

I could try adding nosort to see if it resolves the problem. To be clear, the problem is that in bash, for example, specifying ls {b,a}* implies precedence and we can expect bar to precede ant. This is powerful for setting the order of configuration files.

[isaacs]

@tarwich The reason bash does it that way is that bash is doing an iterative pattern replacement through the pattern string, rather than a recursive directory walk limited by the pattern. While that's very intuitive in a lot of cases, and easy to tie the results back to the pattern that they expanded into, it's also a bit challenging to do in an optimally performant way in JavaScript.

As it happens, glob v9 takes it even further from doing bash pattern expansion, in order to maximize parallelism in the file system walk for performance, and avoid ever testing the same path whenever possible. So, you'll probably have to use some other mechanism for path precedence in the match results, I'm afraid. There's fundamentally no way to get the performance gains in v9 without ditching the string-expansion approach in favor of a recursive fs walk style approach.