-
Notifications
You must be signed in to change notification settings - Fork 544
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@nuxt/ui with strictTemplates enabled causes typecheck errors #2562
Comments
Add the |
nuxt autogenerates "include": [
"./nuxt.d.ts",
"../.config/nuxt.*",
"../**/*",
//...
"../node_modules/.pnpm/@nuxt+ui@3.0.0-alpha.8_@babel+parser@7.26.2_change-case@5.4.4_embla-carousel@8.3.1_ioredis@5._ijev2tcjydqcdikviydmvhkbzq/node_modules/@nuxt/ui/runtime",
"../node_modules/.pnpm/@nuxt+ui@3.0.0-alpha.8_@babel+parser@7.26.2_change-case@5.4.4_embla-carousel@8.3.1_ioredis@5._ijev2tcjydqcdikviydmvhkbzq/node_modules/@nuxt/ui/dist/runtime",
"exclude": [
"../dist",
"../node_modules",
"../node_modules/.pnpm/nuxt@3.14.0_@parcel+watcher@2.5.0_@types+node@22.9.0_ioredis@5.4.1_lightningcss@1.28.1_magica_x3y46x7cew36owemzwsfja6ire/node_modules/nuxt/node_modules",
// ... My point is, that users of nuxt and nuxt/ui shouldn't have to take care of internals of nuxt and nuxt/ui. I don't care, if the solution is a suitable autogenerated |
Why do you use the Since you just want to rely on the generated |
In script you get complaints if you're accessing invalid properties:
That avoids typing mistakes, helps you identify properties that aren't valid any more because the interface changed etc. With
As @hywax has suggested, maybe something is wrong with the config here as type errors within libraries should normally not be reported to the user. As said in #731, it's absolutely not necessary to manually type all the html attributes. This has already been done. For your components, you should be able to merge the types so that the information gets propagated.
We haven't considered Radix Vue as a choice for our ui tooling, but @nuxt/ui. Therefore evaluating @nuxt/ui among others. Using Radix Vue doesn't cause type errors on import.
We want to rely on the autogenerated tsconfig.json as far as possible. As nuxt documentation suggests, the content can be customized to a certain extend. With respect to |
Environment
Version
v3.0.0-alpha.8
Reproduction
https://github.com/some-user123/nuxt-ui-3-typeerrors
Description
npx nuxi typecheck
Expected: no errors
Actually: 35 errors
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: