-
Notifications
You must be signed in to change notification settings - Fork 177
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
Investigate/eliminate barrel files #13618
Comments
|
Hi @swissspidy, I can take this up! |
@Swanand01 The problem here is that all our packages are so intertwined, and basically everything is used, so at the moment I am very skeptical that just changing a smaller package will lead to big improvements right away (at least not in the browser). It might make testing faster, but right now that's not a priority IMO. Plus, considering the hundreds of reported modules above it would be a huge lift to get really significant improvements. So all in all right now it's probably best not to pick it up right away. |
Closing as maybelater |
Task Description
Barrel files can slow down your build/tests, can cause circular dependencies, and makes tree shaking more difficult.
Admittedly, we have a lot of those in the code base.
I was wondering whether we could use something like
eslint-plugin-no-barrel-files
to detect barrel files in in the project to see where they currently have a negative impact.They might not have an impact on our actual bundle size due to better tree shaking, but the difference can be more significant in places like Jest unit tests.
Right now said ESLint rule reports 1502 problems.
The text was updated successfully, but these errors were encountered: