Changelog
Import resolution
Omlet has improved its ability to deduplicate components by resolving component imports across packages. Next up, we'll further improve this through Node.js package entry points.
Alias configuration file
Omlet can now read aliases you have setup in TSConfig files or your bundler to resolve imports. Simply map your aliases in a configuration file. Find out more in our docs.
Updated docs site
We have migrated to a new docs site and added a few sections to address frequently asked questions like…
- How components and their dependencies are detected
- A detailed comparison on Omlet and React Scanner
- An expanded section security
styled-components support
Faster CLI scans
Omlet CLI scan time has been reduced by optimizing how it collects date related information for components.
React Native Support
We now officially support React Native along side React! We hope to continue to expand the teams we can support through different framework support. Reply here if you have a framework you’d like us to support.
Demo Omlet Workspace for Everyone
We prepared a demo workspace (accessible to anyone without an Omlet account) using a real life, open source project called Proton.
Component Dependency Tree Table
Dependency Tree just got another upgrade! We have a new table where you can search for specific components and filter the tree. Confidently updating highly used and complex components is now even easier.
.gif?alt=media&token=d61a40db-1097-4cc1-8adf-94290fbca70a)
Hovers & Interactive Charts
Hover over to learn details about a component in charts and navigate to their detail page directly. Go from usage by project to a list of all components being used in a specific project.
.gif?alt=media&token=57ebcc88-af3f-4725-b44e-d326bb7a7b03)
Magic Link Login with your Email
A secure way to login with Omlet without a password using magic links sent to your email. Signup or invite users with email addresses that are not tied to Google or Github OAuth.
Improved Component Dependency Tree
We’ve updated the component dependency tree and now it’s much easier to see where exactly your components are used, how changes can affect your entire code base.
Auto Tag Components from External Packages
Omlet CLI will now automatically tag components from any external packages like MUI or other libraries as “external”. This will allow you to analyze their usage easily in analytics charts or search them in the component list page.
Windows Support for Omlet CLI
You can now install and run the Omlet CLI on Windows machines as well!
Run Omlet CLI Behind Proxy Server
You can now run Omlet CLI through proxy servers. Pass proxy configuration to the CLI using the HTTP_PROXY and HTTPS_PROXY environment variables.
e.g. HTTP_PROXY=[<http://example.com:1234>](<http://example.com:1234/>) omlet analyze
Filter to Specific Components in Charts
If you’re curious about individual components, you can now analyze specific components in various charts with the new “is” filter.
Lookup Untagged Components in Charts
It is now possible to filter for any untagged components in the charts.
Improved initial setup experience
- Introduced
omlet initwhich will collect necessary repos from the user based on their project setup. - Added UI-based tag configuration page to tag Design System components as Core.
Analytics dashboard with more predefined charts
A new dashboard with several pre-configured charts to show more insights on component usage.
Custom Tags from the CLI have been migrated over to UI-based tagging
Improved Component Detail page
More details about each component are now displayed on the Component Detail page including date-related information, the project it is from, and more.
Project & Date filters in the Component List page
Filter Analytics page based on Component Name or File Paths
.png?alt=media&token=599f412a-7316-4384-b41a-626cb05a6107)
Track Component Date Properties
We now track when components were created, updated and last used. Allowing you to keep a pulse on how your code base and Design system is evolving.
.png?alt=media&token=948f5c5b-c518-4606-bdf8-3d0dd7f054b9)
Filter components by date properties in Analytics page
Curious what custom components your teams are building recently? Filter by created date and custom tag like below. 👇
.png?alt=media&token=5830b661-a365-4be1-a55e-74918921fbea)
Sort components by Created or Updated Date in the Component list page
Now even easier to find specific components to analyze more deeply.
.png?alt=media&token=79c910a2-1720-40c2-bccf-dd3f1807e473)
Untitled
Filter components by dependencies and usage count 🐳
One way you can use this is to find Design System components that have low usage count.
Time series chart for individual components & projects 📈
Track usage increase for new Design System components you release, or find out which projects are adopting your Design System overtime.
Zero config scanning ⚡
You can scan code repositories with no parameters and Omlet will use sensible defaults to provide useful results.
Scan result summary in CLI 🔢
Get a summary of scanned components in the CLI to immediately get feedback.
.png?alt=media&token=4195f771-b459-4c89-ba70-0fd6fb8f35ae)
Untitled
Review Scan History & Delete 🗑️
Ability to review a log of previous scans and delete specific runs to clean the results.
2022-10-19 09.36.59.gif
Improved chart navigation and visualization 💅🏽
Made the popular charts always visible in the analytics page, and improved visualization for breakdowns.
Goodbye
-o / --output . Hello --dry-run 👋The name of the option has been changed and now it will only output results locally to
omlet.out.json
Customizable analytics charts to find actionable insights unique to your team
Customizable Charts ⚙️
.png?alt=media&token=ca710906-aee6-4f46-b8e6-583aa3ac0946)
Untitled
Improved Component Detection
We added support for components detecting dependencies that happen through referencing values in an external object like function calls or other variables.
Fixed Node Dependency Issue
We fixed issue where Omlet CLI was not running on older versions of Node. We officially have a minimum target Node.js version, which is v10.
Fixed Component Usage Detection from Separate Code Repositories
We fixed an issue where the usage of components coming from a separate code repository was not detected. This happens if you scan multiple repositories and one of them is a component library.
Improved analytics and support for tracking multiple code repositories.
Scan Multiple Code Repositories 🗂
If you have multiple products or organize a product into multiple repositories, this will now allow you to track your component usage across all those projects in a single Omlet workspace.
Improved Analytics Charts 📊
Out-of-the-box analytics charts that provide deeper insights into your team's component usage. See adoption across each code repository, adoption over time, and most used components.
.png?alt=media&token=bb236d5f-50fc-4fe8-961b-f8cb3f5683c4)
Untitled
Linux Support 🤖
You can now use Omlet CLI on linux machines.
Tag your components using the CLI to easily group and search them. Further improvements in component detection.
Apply Tags to Categorize Components 🏷
The ability to apply tags to components using Omlet CLI. Use the tags to search and analyze components.
Filter Search with Component Tags 🐳
Use the tags to filter components from the Component Search page
Support for Styled Components 💅
Detect components using Styled Components syntax
Improvements to Monorepo Support 🗂
Support additional Monorepo configurations from Lerna & yarn
Detect Wrapped Components 🎁
Detect and track components that wrapped in various functions
…and many more improvements in component detection and various bug fixes! 👏
Monorepo Support 🗂
Support projects that organized as a monorepo
Detect Components from External Packages 📦
Omlet now detects components coming from external packages/libraries even if they are not part of your source code.
(partial) Support for Styled Components
Omlet can now detect components using Styled Components. We will be improving support for this specific setup further.
Support Alias Imports Using TSConfig Paths 🛣
Better Logs for Troubleshooting 👨🔧
—verbose and —log-level options have been added to Omlet CLI to provide debugging information to diagnose CLI issues.
and many more improvements in component detection and various bug fixes! 👏
Improved Component Detection 💪
Omlet now detects components with class declaration style ex.) class Button extends React. You can also detect components coming from NPM packages.
Component Tree 🌳
When navigating to a Component in Omlet, you will now see a Component Tree that visualizes the dependency of that component.
.png?alt=media&token=1bf79b0d-47dd-4df9-845b-4ce95652449c)
Untitled
Adoption Progress Chart 📊
Omlet will store historical analysis which will be used to keep track of adoption progress under the Analytics page.
.png?alt=media&token=bd29942f-61c7-430d-b9ca-f409fe9a3ecb)
Untitled
User Invite 👨👩👦
You can now invite users to your workspace to share & collaborate.
Auto-upload CLI Output to Omlet Web App ♻️
Omlet CLI will automatically upload the output to the Web app. No need to manually upload the omlet.json file anymore
Login/signup with Google or GitHub OAuth 🔐
You can now log in (or register) using your Google or GitHub accounts.
Last modified 3d ago