We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
All non-globby names are migrated to the front of the array and all globby names are placed after the non-globby names.
If I have this array:
[ '*.js', '*.css', 'app.html' ]
Then the resulting file list will have 'app.html' listed first even though I asked for it last.
The text was updated successfully, but these errors were encountered:
Hello, @intervalia,
This is the correct behavior described in the README.md.
README.md
This package does not respect the order of patterns. First, all the negative patterns are applied, and only then the positive patterns.
You can use one of the sorting methods. For example, by .sort.
.sort
Sorry, something went wrong.
Unfortunately, we cannot guarantee consistency in the current version of the package.
But you can use the hack.
const fg = require('fast-glob'); const first = fg(['app.html']); const second = fg(['*.js', '*.css']); Promise.all([first, second]).then(([a, b]) => [].concat(a, b));
is not a valid value for v-model
mrmlnc
No branches or pull requests
Environment
Actual behavior
All non-globby names are migrated to the front of the array and all globby names are placed after the non-globby names.
Expected behavior
If I have this array:
[ '*.js', '*.css', 'app.html' ]
Then the resulting file list will have 'app.html' listed first even though I asked for it last.
The text was updated successfully, but these errors were encountered: