A set of reusable elements that enable Virtru designers and Virtru engineers to create consistent Virtru products.

Usage no npm install needed!

<script type="module">
  import virtuosoDesignSystem from '';


Virtuoso Design System

Validate PR Release Deploy Storybook

This repo enables using the Virtuoso Design System as front-end code (HTML, CSS, & JavaScript).

This project is not a common place for library reuse. For instance charts and graphs should be added to the app directly. For charting we suggest nivo charts.

📖 Dive into the docs

🤖 Explore the code


The documentation for Virtuoso is hosted on GitHub Pages and powered by Storybook.

To run storybook locally:

npm run storybook


🚨 Virtuoso is still a work in progress and installation instructions are limited.


To install with Create React App you will need to use Craco (Create React App Configuration Override).

  1. Install Craco npm i --save-dev craco
  2. Install Craco-Antd plugin npm i --save-dev craco-antd
  3. Install Virtuoso and Antd npm i --save virtuoso-design-system antd
  4. Create a .cracorc.js and add the config
  5. Use Virtuoso


// .cracorc.js
const { when, whenDev, whenProd, whenTest, ESLINT_MODES, POSTCSS_MODES } = require("@craco/craco");
const CracoAntDesignPlugin = require("craco-antd");
const VirtuosoTheme = require('virtuoso-design-system/dist/antd')

module.exports = {
  plugins: [
      plugin: CracoAntDesignPlugin,
      options: {
        customizeTheme: VirtuosoTheme


import React from 'react';
import { Button } from 'virtuoso-design-system';

export default function MyComponment() {
 return <Button>Hi there!</Button>

Design Tokens

Design tokens are the visual design atoms of the design system — specifically, they are named entities that store visual design attributes. We use them in place of hard-coded values (such as hex values for color or pixel values for spacing) in order to maintain a scalable and consistent visual system for UI development.

Salesforce Lightning Design System

Style Dictionary is a build system that allows you to define design tokens once, in a way for any platform or language to consume.

  1. Our design tokens are defined in lib/styles/style_dict/tokens/ as JSON files…

  2. …read by the config in lib/styles/style_dict/config.json

  3. …and built by the command

npm run style-dictionary:build
  1. …which creates lib/styles/build/ files for CSS, JS, or whatever platform needs them.

  2. You can clear the built tokens with

npm run style-dictionary:clean


Examples can be found in /examples


Releases are handled by Auto.

  1. Please tag your PRs "release" in order for Auto to find them.

  2. Then, all you have to do is npm run release and you'll get:

  • automatic changelog
  • bump npm version
  • publish to npm — based on your npm login or NPM_TOKEN in .env
  • make a GitHub release — based on your GH_TOKEN in .env

This works with the magic described in auto shipit docs.

A static version of the Storybook docs are generated automatically before we publish releases to npm.

Development & Testing & Updating

To develop new components make sure to:

  • add components to /lib/components
  • add helpers and hooks to /lib/helpers
  • add relevant stories to /stories
  • add tests next to the component

Run locally

npm run storybook

Run tests

npm run test

Visual Regression Testing (VRT)

This repository uses Loki for VRT to ensure the visual appearance of states of the components does not regress. Baseline reference images are intentionally checked into this repository in .loki/reference/.

Running VRT locally

You can run the VRT tests locally to check to see if your changes have caused visual regressions from the existing baselines for all components based on the loki config in package.json:

npm run test:vrt

For faster results, you can run a subset of tests using --storiesFilter:

npm run test:vrt -- --storiesFilter=Input

Any failed tests will be output in .loki/difference/. You can inspect any visual differences that are highlighted in these output images.

If the differences are intended, you can update the baselines by following the instructions in the next section.

Updating Loki Baselines

Note: Before performing this step, you must first run the VRT once (see previous section).

If you run the tests above and have legitimate changes in the visual appearance of the components, you can approve new baselines, which will replace the existing baseline images with the new, current images:

npx loki approve

This will immediately take all new baseline images from the last test run and replace the existing baseline images. If you wish to update a specific test case image only but reject other changes, see the Loki CLI reference.

We recommend only approving new baselines once all unintended visual changes have been fixed, then running the command above so no fine-grained filtering of new baselines is needed.

Copyright © 2020 Virtru Corporation