Closed aussieboi closed 1 year ago
@aussieboi handsome young man,I like your proposal,But I haven't figured out how to do this while maintaining good development performance。
In addition, two modules may have the same variable name export, which will confuse the import
@markthree tnx, I just saw PR from Anthony Fu for nuxt he uses https://github.com/unjs/mlly maybe it can help will help, will have more time over weekend so I can try with a PR if you are open for it.
In addition, two modules may have the same variable name export, which will confuse the import
Can add warning/error so dev will need to resolve this. conflict
@aussieboi amazing,Welcome PR, but I hope it becomes an option
sry got busy, will try to check it soon.
@aussieboi Don't be nervous. I'll pay attention whenever you have time to mention pr。😁
Since unplugin-auto-import supprots dirs
options i switched back to it, won't be needing this feature, as time is hectic right now, so not time for adding something like that.
Sry if somebody want's play with this feel free will be here and follow issue.
@aussieboi Thank you for your information
Currently there is option to auto import composable that are only exported as default export
bar
won't be able to be avaiable for autoimport, Yes I can add ne composable, but in some cases it would be better to have in same file cause they in same context, and its better for tree-shaking.Food for thought.