chore: switch to tinyglobby (#705)

https://npmgraph.js.org/?q=fast-glob - 17 dependencies
https://npmgraph.js.org/?q=tinyglobby - 2 dependencies

Author: benmccann

README.md

@@ -402,7 +402,7 @@ const umzug = new Umzug({
 
 Note on migration file sorting:
 
-- file matches, found using [fast-glob](https://npmjs.com/package/fast-glob), will be lexicographically sorted based on their paths
+- file matches, found using [tinyglobby](https://npmjs.com/package/tinyglobby), will be lexicographically sorted based on their paths
   - so if your migrations are `one/m1.js`, `two/m2.js`, `three/m3.js`, the resultant order will be `one/m1.js`, `three/m3.js`, `two/m2.js`
   - similarly, if your migrations are called `m1.js`, `m2.js`, ... `m10.js`, `m11.js`, the resultant ordering will be `m1.js`, `m10.js`, `m11.js`, ... `m2.js`
 - The easiest way to deal with this is to ensure your migrations appear in a single folder, and their paths match lexicographically with the order they should run in
@@ -414,7 +414,7 @@ The Umzug class should be imported as a named import, i.e. `import { Umzug } fro
 
 The `MigrationMeta` type, which is returned by `umzug.executed()` and `umzug.pending()`, no longer has a `file` property - it has a `name` and *optional* `path` - since migrations are not necessarily bound to files on the file system.
 
-The `migrations.glob` parameter replaces `path`, `pattern` and `traverseDirectories`. It can be used, in combination with `cwd` and `ignore` to do much more flexible file lookups. See https://npmjs.com/package/fast-glob for more information on the syntax.
+The `migrations.glob` parameter replaces `path`, `pattern` and `traverseDirectories`. It can be used, in combination with `cwd` and `ignore` to do much more flexible file lookups. See https://npmjs.com/package/tinyglobby for more information on the syntax.
 
 The `migrations.resolve` parameter replaces `customResolver`. Explicit support for `wrap` and `nameFormatter` has been removed - these can be easily implemented in a `resolve` function.
 

package.json

@@ -17,8 +17,8 @@
 	"dependencies": {
 		"@rushstack/ts-command-line": "^4.12.2",
 		"emittery": "^0.13.0",
-		"fast-glob": "^3.3.2",
 		"pony-cause": "^2.1.4",
+		"tinyglobby": "^0.2.13",
 		"type-fest": "^4.0.0"
 	},
 	"devDependencies": {

pnpm-lock.yaml

@@ -1,5 +1,5 @@
 import emittery from 'emittery'
-import {glob} from 'fast-glob'
+import {glob} from 'tinyglobby'
 import * as fs from 'fs'
 import * as path from 'path'
 import * as errorCause from 'pony-cause'
@@ -494,7 +494,7 @@ export class Umzug<Ctx extends object = object> extends emittery<UmzugEvents<Ctx
     const resolver: Resolver<Ctx> = inputMigrations.resolve ?? Umzug.defaultResolver
 
     return async context => {
-      const paths = await glob(globString, {...globOptions, ignore, absolute: true})
+      const paths = await glob(globString, {...globOptions, ignore, expandDirectories: false, absolute: true})
       paths.sort() // glob returns results in reverse alphabetical order these days, but it has never guaranteed not to do that https://github.com/isaacs/node-glob/issues/570
       return paths.map(unresolvedPath => {
         const filepath = path.resolve(unresolvedPath)