Future scans

Learn how to scan more repositories with CLI's analyze command.

If you made changes to the repositories you previously scanned or need to add more repositories to your analyses, you can scan them using the analyze command.

npm

npx @omlet/cli analyze

yarn

yarn dlx @omlet/cli analyze

pnpm

pnpm dlx @omlet/cli analyze

Omlet will automatically detect the previously scanned components and update them as needed. It'll also match components defined in one repo and used in another.

Common questions about CLI scans

What happens to the previous scans?

Omlet keeps your adoption charts up-to-date by tracking component changes across your projects. Removed components? No problem, the usage numbers will adjust automatically.

Historical charts benefit from previous scans. You'll continue to have snapshot data from a specific date to understand how your design system evolves.

How often should we scan the codebase?

There's no limit to your scans. We recommend scanning when there are changes to your projects and the design system.

Should we scan everything at once?

Not necessarily. You can scan additional repositories anytime you want. Omlet can match the component relationship between the recently and previously scanned components.

Next steps

We recommend checking the Ensure data accuracy page and having the required CLI configuration to ensure you have accurate component data from your scans.

Once you're happy with the results, you can set up regular scans and run Omlet as part of your build process or with scheduled intervals.