N

Nuxt•8mo ago•

5 replies

dmarr

Types added via module

I am reading https://nuxt.com/docs/guide/going-further/modules#adding-type-declarations and trying to understand something. I have a type that I want "exported" from my module, or at least "known" when something needs to introspect a property in the app. I don't really understand the mechanics here. In the example they declare module 'nitropack'declare module 'nitropack' I guess because they are overriding/extending something exposed in nitro. In my case, if I just want the type to be discoverable (both within the module and outside it), do I use declare 'global'declare 'global' or what?
I see my nuxt.d.ts and it has the /// <reference path="types/my-module.d.ts" />/// <reference path="types/my-module.d.ts" /> there, but the types I declare there are not found in my app. I did see a comment from Daniel saying that TS types aren't Autoimportable by design, so maybe I am barking up the wrong tree or my approach is not correct.
Can anyone point me to somewhere I can go to better understand this stuff? I feel like such a luddite when it comes to TS and these types of issues don't help.

Nuxt

Module Author Guide · Nuxt Advanced

Learn how to create a Nuxt Module to integrate, enhance or extend any Nuxt applications.