Omlet is an analytics tool to help you measure the success of your component libraries and design system and identify opportunities to improve it. 🍳 *Now in public beta, supports React
Omlet is a component analytics tool for React. You can now use Omlet directly in VS Code and analyze how and where your React components (and their props) are used as you're coding — helping you confidently update, clean up and maintain your component library.
Hey folks, Berk here from the Omlet crew. I'm one of the co-founders. 👋
Today, we're super excited to announce Omlet for VS Code — our biggest update since launch!
You can now analyze how and where your React components (and their props) are used right inside your editor — helping you confidently update, clean up, and maintain your component library, reducing tech debt along the way.
Get started at https://omlet.dev/extension and let us know what you think — we're just getting started so any feedback would be super helpful.
Cheers!
This is a great way to streamline development—being able to track how and where components are used directly within the editor will save so much time and reduce the risk of errors. How does Omlet handle situations where components are used in complex or deeply nested structures—does it still provide clear visibility for those cases?
Omlet is designed to handle most complex and deeply nested component scenarios, clearly identifying not only the usage but also prop values. In those rare cases where we're unable to fully detect the specific usage details, we still reliably detect and resolve imports. This ensures that component relationships remain clear and properly captured even in complex situations.
If you run into issues, let us know though, happy to help!
Omlet for VS Code looks like a huge productivity boost for React devs! 🔥 Being able to track component usage and props right inside the editor is a game-changer for maintaining a clean, efficient codebase. This will definitely help teams reduce tech debt and refactor with confidence. Congrats on the launch! 🚀 Looking forward to trying it out.
Zeplin
Fable Wizard
This is a great way to streamline development—being able to track how and where components are used directly within the editor will save so much time and reduce the risk of errors. How does Omlet handle situations where components are used in complex or deeply nested structures—does it still provide clear visibility for those cases?
Omlet
@jonurbonas thank you so much for the kind words!
Omlet is designed to handle most complex and deeply nested component scenarios, clearly identifying not only the usage but also prop values. In those rare cases where we're unable to fully detect the specific usage details, we still reliably detect and resolve imports. This ensures that component relationships remain clear and properly captured even in complex situations.
If you run into issues, let us know though, happy to help!
Omlet for VS Code looks like a huge productivity boost for React devs! 🔥 Being able to track component usage and props right inside the editor is a game-changer for maintaining a clean, efficient codebase. This will definitely help teams reduce tech debt and refactor with confidence. Congrats on the launch! 🚀 Looking forward to trying it out.
Zeplin
That's awesome to hear, thanks @mihajlo_kuzmanoski — feel free to ping us anytime if you have any feedback!