Bug: fs.promises.glob incorrect return typing

[dylnic]

The return typing of fs.promise.glob in memfs is incorrect. It returns Promise<string[]> instead of NodeJS.AsyncIterator<string>

memfs:

glob: (pattern: string, options?: opts.IGlobOptions) => Promise<string[]>;

Node typing:

/**
 * ```js
 * import { glob } from 'node:fs/promises';
 *
 * for await (const entry of glob('*.js'))
 *   console.log(entry);
 * ```
 * @since v22.0.0
 * @returns An AsyncIterator that yields the paths of files
 * that match the pattern.
 */
function glob(pattern: string | readonly string[]): NodeJS.AsyncIterator<string>;
function glob(
    pattern: string | readonly string[],
    options: GlobOptionsWithFileTypes,
): NodeJS.AsyncIterator<Dirent>;
function glob(
    pattern: string | readonly string[],
    options: GlobOptionsWithoutFileTypes,
): NodeJS.AsyncIterator<string>;
function glob(
    pattern: string | readonly string[],
    options: GlobOptions,
): NodeJS.AsyncIterator<Dirent | string>;

[ext]

Got hit by this as well. The workaround I found was to await twice:

/* eslint-disable-next-line @typescript-eslint/await-thenable -- memfs returns a promise instead of async iterator*/
for await (const entry of await fs.glob(pattern)) {
  /* ... */
}

Would be nice if this could be fixed directly in memfs though.