RAD

Recess Analytics Dashboard

Recess Analytics Dashboard (RAD) is an internal tool for Guild built and maintained by Recess & Accessibility (R&A) under Platform Engineering.

It has been developed to provide better observability of how squads are using the Recess Design System (Recess DS).

Questions? Comments? Feature requests?

Reach out to the R&A squad in #recess on Slack.

Frequently Asked Questions:

What version of Recess packages, Typescript, and React, is my project loading?

Go to Guild Project Dependencies

How are squads using components in their repos, and where?

Go to Component Usage

Can I discover how/what props are being used for a specific component?

From the Component Usage page, filter to the desired component you want to check props usage. Click on the link in the lower left hand corner of one of the code block cards in the results.

Go to Component Usage

Why do I see duplicate packages when I look at my repo’s dependency data?

RAD scans a project’s yarn.lock file for dependencies, which represents the entire dependency tree, including in-direct dependencies. These dependencies of dependencies can result in projects requiring multiple versions of the same package. This was intentional as it allows people to understand potential issues with conflicting versions or large load sizes. Including micro-frontends (MFE) in your project will often introduce duplicate dependencies.

Where does R&A pull the data from?

RAD gathers data from Guild's internal GitHub organization. It clones each repository and traverses the codebase to find uses of internal Guild packages along with a few other packages that are considered valuable.

After dependency analysis, each project is cloned through Github and traversed for uses of Recess components. Each JSX file is broken into an AST and examined for matching imports and invocations from the Recess package to accomplish this.