Skip to main content

0.6.1 Release

ยท 5 min read
Casey Baggz

New React components, a11y libs, and a bright future ahead! ๐Ÿ”ฅ


We are excited to announce some new React components that are now available for you to use in your apps!

New Componentsโ€‹


First up is the ActionMenu which brings together a submit button and a dropdown menu into one component. This is a first to Pluralsight but is commonly used all over Github.


For...when you need to iterate over some data, we have the For component which is another Solid-JS inspired API that helps you render a list in a declarative (code base) and performant (customer experience) way.


Last, we have the Tabs family which is a set of components that help you build a tabbed interface. Fun fact, it also handles heavy data loading for you!

Developer Experienceโ€‹

The new APIs also ship JSDOC comments to help you understand how to use the components right where you are in your IDE.

We have also updated the build process so you can import types from the library directly. This means you can now do this:

import { For, type ForProps } from '@pluralsight/react'

From this point forth, all of the Pando packages will use this build process.

Future features?โ€‹

We are about almost feature complete for our v1 release. The only thing we are missing is a few more components mentioned in our Library Status Discussion. We are closer than ever!

But that's not all for React! We have a few more things to announce...


We have officially launched our React-aria library which is a set of high performant React hooks that help you build accessible components. This is used internally in the React library so there is no need to install it when using Pando.

As Pando has matured we have realized that we need to start separating our a11y and styles libraries. This is the first step in that direction.

The new APIs also ship JSDOC comments to help you understand how to use the components right where you are in your IDE.


With the introduction of React-aria, we can now update our Headless-styles library to own only styling which will help the library scale long-term. We have started this migration with the new components mentioned above.

The new APIs also ship JSDOC comments to help you understand how to use the components right where you are in your IDE.

What's Next?โ€‹

We have very BIG changes in store for our future. This means that we will probably ship one more minor release that contains the final components for the React lib, then we will be moving to the official v1 release.

v1 Releaseโ€‹

We are planning on releasing v1 in the next few months and will bring a new developer experience that is the best Pando (or Pluralsight) has ever seen. Here is the high level details of what you can expect:

Pando CLIโ€‹

In v1, we will be introducing a new CLI that will help streamline using Pando. This will help you setup and maintain anything Pando related in your app through automation. โœŠ

Example of a future command:

npx pando setup --typescript

This command would setup your app with all the necessary configs and dependencies to use Pando with Typescript. Likewise, we will have a command that will help you migrate from version to version. ๐ŸŽ‰

Panda CSS ๐Ÿผโ€‹

In v1, Headless styles will migrate to Panda CSS which will help create consistency across all of our teams regarding styling libraries. This means that each user of Pando should only use Panda CSS for styling. Panda does what Headless-styles was meant to do long-term and is very easy and scalable to use. Likewise, it natively supports close to any JSX-like syntax (including Svelte) which means that if and when we need to switch technologies - teams can still use Pando without worry.

The CLI above will install and setup a panda.config.ts file for you to use in your app. This will allow your team to have a solid styling foundation that is both easy to use and scale whenever your team needs to deviate from Pando.

Github Actionsโ€‹

We will also be introducing a Github Actions workflow to help quality check our code-bases to ensure everyone is on the latest version of Pando and only using Panda-CSS. ๐Ÿš€

One of our biggest goals with Pando is to help provide a stable structure for the styling FE tech stack at Pluralsight. This is very big problem with the current product that is loading anywhere from up to 5 different styling libraries at once. ๐Ÿ™…โ€โ™€๏ธ

This will help us ensure that we are delivering as high performant of a product for our customers as possible, while also making it easy for our teams to build new features and context switch successfully if there is ever a need for teammates to move around.

Future Ideasโ€‹

Interested in where we are going or have a new idea of your own? Create a new discussion or submit a new RFC!

Want to help us get to v1 faster? We are always looking for more contributors! Check out our Contributing Guide to get started.

Thanks ๐ŸŽ‰โ€‹

This release wouldn't be possible without the contribution of all the teams who have already started using the React library in addition to contributing to our RFC for the design of it!


If it is your first time using any of our packages, check out our Installation Guide.

npm install @pluralsight/{react,headless-styles,icons}@0.6.1

As always, if you have any questions or ideas, please drop us a thread in our Discussions Page.