This is a pattern I've found extremely nice to use compared to explicitly importing n nested functions/variables.
https://github.com/bencoveney/barrelsby
With a Vue project, the unplugin-vue-components Vite plugin performs a similar function for components, but I've found working with Vulk and Vuero that for the TypeScript imports there tends to be a huge stack of imports for even fairly simple scenarios.
The one directory where I've found it does not make sense to implement is the stores directory. Often stores will reference each other and due to how some (WebStorm) optimises imports, it will always attempt to use the shortest path. When using the /@src/ stub this can accidentally create circular dependencies that stores are particularly affected by.
Just a suggestion, so of course just close if explicit imports are a deliberate design decision.
This is a pattern I've found extremely nice to use compared to explicitly importing
nnested functions/variables.https://github.com/bencoveney/barrelsby
With a Vue project, the
unplugin-vue-componentsVite plugin performs a similar function for components, but I've found working with Vulk and Vuero that for the TypeScript imports there tends to be a huge stack of imports for even fairly simple scenarios.The one directory where I've found it does not make sense to implement is the
storesdirectory. Often stores will reference each other and due to how some (WebStorm) optimises imports, it will always attempt to use the shortest path. When using the/@src/stub this can accidentally create circular dependencies thatstoresare particularly affected by.Just a suggestion, so of course just close if explicit imports are a deliberate design decision.