Omlet recently announced that they are open-sourcing their React library analytics product, and making it available for self-hosting.
We currently face a significant data gap regarding how components in the React library are being used in the wider organization (compared to Figma's library analytics.)
We should investigate whether Omlet can help plug this gap.
There are some limitations/potential blockers to consider:
- Omlet runs scans locally from the CLI, which limits its reach and potentially makes automating or integrating it into CI/CD challenging
- In limited testing, there are some issues with data accuracy (e.g. duplication of components depending on how and where they're imported and used)
- Self-hosting documentation is currently relatively limited, and it's unclear whether the product will be supported going forward
I've done some initial exploration on this branch: https://github.com/bcgov/design-system/tree/feature/omlet
- Import the Omlet repo as a submodule
- Add basic config for for @bcgov/design-system-react-components
Omlet recently announced that they are open-sourcing their React library analytics product, and making it available for self-hosting.
We currently face a significant data gap regarding how components in the React library are being used in the wider organization (compared to Figma's library analytics.)
We should investigate whether Omlet can help plug this gap.
There are some limitations/potential blockers to consider:
I've done some initial exploration on this branch: https://github.com/bcgov/design-system/tree/feature/omlet