chore: add index.ts to module starter

[Atinux]

Explain that module authors can expose utils outside of Nuxt context for end users.

Actually I believe this does not work at all 🤔

• package exports:

  starter/package.json

  Lines 8 to 14 in 358482c

  	".": {
  	"types": "./dist/types.d.ts",
  	"import": "./dist/module.mjs",
  	"require": "./dist/module.cjs"
  	}
  	},
  	"main": "./dist/module.cjs",

When running npm run prepack:

[codesandbox]

  Open in CodeSandbox Web Editor | VS Code | VS Code Insiders

[Tahul]

Few context for this:

Few issues I remember from exporting your module utils from the same path as your defineNuxtModule:

• These utils will have to be server/build time only, because the file will inevitably ship @nuxt/kit
• If that file happen to be imported in a jiti context, @nuxt/kit will be inlined with the jiti(path)
  • (not sure if this one is still true)

What I usually do from my modules is a /utils export, or exporting my module from /nuxt or /module

[Atinux]

Thank you @Tahul

It just seems a black box where no one as a simple answer to this. Will just close this issue and hope that no one will have to expose utils outside of the module

[danielroe]

All imports meant to be imported within the user's Vue app should be in the runtime directory instead and exposed with a subpath export or directly through nuxt core utils like addImportsDir, addComponent, etc. Exports from index.ts are only meant to be used in your nuxt.config or otherwise in the build environment.

[pi0]

I have opened #292 to continue on this discussion.

The module structure is intentionally opened to allow exposure to other integrations. Today, it is only possible via aliases for runtime and a mixed output for build time utils (via dist/module.*) shared between modules.