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
Labels
P3
Nice to have
Type: Code Quality
Things that need a refactor, rewrite or just some good old developer ❤️
Type: Infrastructure
Changes impacting testing infrastructure or build tooling
Type: Performance
Performance related issues and enhancements.
Comments
swissspidy
added
Type: Infrastructure
Changes impacting testing infrastructure or build tooling
Type: Performance
Performance related issues and enhancements.
P3
Nice to have
Type: Code Quality
Things that need a refactor, rewrite or just some good old developer ❤️
labels
Apr 16, 2024
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
P3
Nice to have
Type: Code Quality
Things that need a refactor, rewrite or just some good old developer ❤️
Type: Infrastructure
Changes impacting testing infrastructure or build tooling
Type: Performance
Performance related issues and enhancements.
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: