Typescript is not recognized well

[cesxhin]

I updated to version 1.0.1 and I'm having a problem recognizing the typescript structure of the components.

For example now in my project in the file: ".nuxt/components.d.ts"
there is a component of the module that I made but it tells me any.

Instead I have another library (also made by me) and it recognizes very well and I have not updated module-builder.

UPDATED

If I specify .d.ts in the ".nuxt/components.d.ts" file instead, it works.

export const FormFields: typeof import("../node_modules/@xxxxxx/fields-loader/dist/runtime/components/formFields.vue.d.ts")['default']

Current settings package.json:

[...]
"exports": {
    ".": {
      "types": "./dist/types.d.mts",
      "import": "./dist/module.mjs"
    },
    "./components/*": "./dist/runtime/components/*",
    "./utils/*": "./dist/runtime/utils/*"
  },
  "main": "./dist/module.mjs",
  "typesVersions": {
    "*": {
      ".": [
        "./dist/types.d.mts"
      ],
      "components/*": [
        "./dist/runtime/components/*.d.ts"
      ],
      "utils/*": [
        "./dist/runtime/utils/*.d.ts"
      ]
    }
  },
  "files": [
    "dist"
  ],
[...]

[quantix-dev]

I tried making a minimal reproduction and this seems to work for me (no type errors).
https://stackblitz.com/edit/nuxt-module-builder-x983ks

Instead I have another library (also made by me) and it recognizes very well and I have not updated module-builder.

I'm using file modules in the playground to replicate your environment,
It seems to be working fine.

It is important to note you can't do .default on a type in TypeScript. It must be indexed with square brackets ['default']
https://www.typescriptlang.org/docs/handbook/2/indexed-access-types.html

[danielroe]

Would you be able to provide a reproduction? 🙏

[github-actions]

We cannot recreate the issue with the provided information. Please add a reproduction in order for us to be able to investigate.

Why was this issue marked with the needs-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. Please provide a link to either :

• a public GitHub repository
• a CodeSandbox
• a StackBlitz.

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

What happens if I don't provide a sufficient minimal reproduction?

Issues with the needs-reproduction label that receives no meaningful activity (e.g. new comments with a reproduction link) will be closed by the maintainers and won't be looked at.

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps. Furthermore, you can upvote the issue using a reaction on the topmost comment.

• Please do not comment "I have the same issue" without repro steps
• Please do not comment un-helpful messages such as "+1" on an issue, use reactions on the first comment instead.

I think my reproduction is good enough, why aren't you looking into it quicker?

We constantly monitor open issues for new comments.

However, sometimes we might miss one or two. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible.

I have a minimal reproduction to contribute to a closed issue.

If you have a minimal reproduction for a closed issue, please write a comment on the issue with a link to the reproduction.
We will review it and reopen the issue if it is sufficient.

Useful Resources

• Why reproductions are required
• How to create a Minimal, Complete, and Verifiable example

[hanneskuettner]

Seems like this problem is also plaguing the most recent NuxtUI 3.1.0 release, see nuxt/ui#3973 for the corresponding NuxtUI issue and this code sandbox as a reproduction https://codesandbox.io/p/devbox/flamboyant-scott-k7p4kv. In the sandbox I try to import the ButtonProps from NuxtUI.

In a previous version of NuxtUI build with @nuxt/module-builder 0.8.4 the same import works, see https://codesandbox.io/p/devbox/gracious-https-84vh6c

[danielroe]

I can't access that link.

[hanneskuettner]

I can't access that link.

Whoops. Mind giving it a second try? Was still on private by default.

[hanneskuettner]

Here is another Stackblitz reproduction with the same setup: Nuxt starter Stackblitz + NuxtUI built with @nuxt/module-builder@1.0.1: https://stackblitz.com/edit/github-hdv1fzks?file=package.json,app.vue

[danielroe]

Can you reproduce without Nuxt UI?

(The issue might be to do with nuxt/ui rather than the module builder.)

https://arethetypeswrong.github.io/?p=%40nuxt%2Fui%403.1.1