Analyze custom styles usage in the project.
We shouldn’t use custom styles on the application level. We should compose our user interfaces from primitive components. Sometimes, a component library isn’t flexible enough to make it possible, especially when it’s young.
By analyzing custom styles usage in the application and finding which component’s styles developers override the most, we can find what’s missing in the component library: missing component props, missing design tokens, and so on.
- JavaScript files
- TypeScript and Flow files
- styled-components and Emotion (
styled
factory) -
sx
andcss
props (Theme UI) - CSS
- CSS Modules
- Sass
- Custom styles per module
- Overridden elements
- Overridden components
- CSS properties
- CSS values
- Custom colors (very basic, needs more work)
- Custom spacing
- Components and props
- Components, props and values
npm install antbear
npx antbear 'src/**/*.{js,ts,tsx}'
The changelog can be found on the Releases page.
Everyone is welcome to contribute. Please take a moment to review the contributing guidelines.
Artem Sapegin and contributors.
MIT License, see the included License.md file.