fix: update package exports types

[happy-turtle]

Export the package's runtime types instead of only the module's configuration types in the package's exports field.

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

With this I want to get back to #244, which isn't quite fixed yet. Currently the package only exports the ModuleOptions types. Hence with moduleResolution type bundler (introduced with the latest Nuxt versions), it is not possible to e.g. import type { DirectusFile } from 'nuxt-directus' without type errors. This change ensures to export the runtime types instead of only the module's configuration types.

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes (if not applicable, please state why)

Tested on a local Nuxt v3.12.2 with typescriptBundlerResolution: true.

[vercel]

@happy-turtle is attempting to deploy a commit to the Conner's projects Team on Vercel.

A member of the Team first needs to authorize it.

[sandros94]

First of, thanks for opening this PR.

Indeed exporting runtime's types would be useful, but I'm afraid this is not the right way. This is mainly because of how defineNuxtModule generates schema types (if my understandings of it are correct).

But, as always, there are other options:

• create an alias much like @nuxt/ui does it and import then as needed from #ui/types
• or directly export all types from within module.ts itself by simply adding this after all the imports:

  export type * from './runtime/types'

Considering the current structure I would go for the latter one, @happy-turtle could I ask you to do these changes?

[happy-turtle]

That sounds pretty reasonable, thanks for your feedback. I will update the PR according to your second suggestion 👍

[sandros94]

LGTM!