You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm a relatively new Nuxt 3 user, and one thing that always foxes me is auto-imports.
Although it's great that Nuxt auto-imports, the down-side is I don't know what is available, what or where it's from, or what package it belongs to. Sometimes I just look in the imports.d.ts file just to see, but it's just a big list of names.
However, if the declarations were grouped by folder, I think it would be a nice hint for those of us looking behind the curtain.
I wrote a quick and dirty node script to see what it might look like, and I think it's super helpful already:
Describe the feature
Hi Unimport team.
I'm a relatively new Nuxt 3 user, and one thing that always foxes me is auto-imports.
Although it's great that Nuxt auto-imports, the down-side is I don't know what is available, what or where it's from, or what package it belongs to. Sometimes I just look in the
imports.d.ts
file just to see, but it's just a big list of names.However, if the declarations were grouped by folder, I think it would be a nice hint for those of us looking behind the curtain.
I wrote a quick and dirty node script to see what it might look like, and I think it's super helpful already:
Think this is something you could build in to the generation function?
Additional information
The text was updated successfully, but these errors were encountered: