Why you probably shouldn't be adding index.ts files everywhere

TK Dodo is a platform dedicated to sharing insights and resources on software development, technology trends, and career growth. Through articles, interviews, and community engagement, TK Dodo empowers developers to navigate their career paths, stay updated with industry advancements, and cultivate  skills for personal and professional development.

TkDodo

In a discussion on proper file organization in frontend development, the author argues against using barrel files in JavaScript and TypeScript projects. Barrel files, which re-export components from a single file, can lead to circular imports and decreased development speed due to unnecessary module loading. While useful in library entry points, they create complications in application code, making it harder to manage imports and debug errors. Instead, consistent and straightforward import practices are recommended.

Please Stop Using Barrel Files

I agree with the author.
In times when IDEs do the imports (semi-)automatically and no one needs to write import paths, barrel files are a waste of effort.
The only positive of them would be a weak indication of publicness of module members. The trade-offs are bad, though.

They caused me so much trouble when one of the apps I worked on scaled up. They where supposed to help but instead ended up being a maintenance chore, something we needed to check in PRs, etc. eventually no one maintained them and they just kind of fell out of the project.

I understand the problem, but you can have cases where it is useful.
I used it like a namespace for my entities in my application based on a clean architecture. That allow me to access easily to my entities without importing 15 files, and for the last year, I never encountered a problem while updating code.
But in fact in a lot of case it could be problematic

Due to the use of barrel files in NestJS, developers began importing from both the barrel files and directly from individual files, leading to significant issues with circular dependencies, as many files were already imported in the barrel file. We have now moved away from using barrel files (as also recommended in the NestJS documentation), and this programming paradigm applies to other JavaScript frameworks as well.

Way ahead of ya! don’t even know what they are!