fix(useFileDialog): type UseFileDialogReturn

[xiaoxiangmoe]

Description

/// <reference types="node" />
export interface UseFileDialogOptions extends ConfigurableDocument {
  /**
   * @default true
   */
  multiple?: boolean
  /**
   * @default '*'
   */
  accept?: string
  /**
   * Select the input source for the capture file.
   * @see [HTMLInputElement Capture](https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/capture)
   */
  capture?: string
}
/**
 * Open file dialog with ease.
 *
 * @see https://vueuse.org/useFileDialog
 * @param options
 */
export declare function useFileDialog(options?: UseFileDialogOptions): {
  files: Readonly<
    Ref<{
      readonly [x: number]: {
        readonly lastModified: number
        readonly name: string
        readonly webkitRelativePath: string
        readonly path: string
        readonly size: number
        readonly type: string
        readonly arrayBuffer: {
          (): Promise<ArrayBuffer>
          (): Promise<ArrayBuffer>
        }
        readonly slice: {
          (
            start?: number | undefined,
            end?: number | undefined,
            contentType?: string | undefined
          ): Blob
          (
            start?: number | undefined,
            end?: number | undefined,
            contentType?: string | undefined
          ): Blob
        }
        readonly stream: {
          (): ReadableStream<Uint8Array>
          (): NodeJS.ReadableStream
        }
        readonly text: {
          (): Promise<string>
          (): Promise<string>
        }
      }
      readonly length: number
      readonly item: (index: number) => File | null
      readonly [Symbol.iterator]: () => IterableIterator<File>
    } | null>
  >
  open: (localOptions?: Partial<UseFileDialogOptions>) => void
  reset: () => void
}

This type has type error in browser because NodeJS.ReadableStream is needed.

        readonly stream: {
          (): ReadableStream<Uint8Array>
          (): NodeJS.ReadableStream
        }

Additional context

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.