Common webcomponents

Downloads in past


3.34.03 hours ago4 months agoMinified + gzip package size for genesys-spark-components in KB


Spark Web Components
This repo contains the CSS and custom elements that make up Genesys' design system, Spark.

Component Evolution

At any given time there are three types of components present in the library:
  • stable: Most components fall into this category, and there will be no breaking api changes outside of a major release.
  • beta: New components where the API design is still being explored. Breaking changes may happen without a major version change.
  • legacy: Old components that have been replaced by a new component, or a newer version of the component with an incompatible API. These will be removed in the next major release.

For more details on the component evolution process see the full documentation on the topic


Lives here

Installing the library


npm install genesys-spark-components
yarn add genesys-spark-components

Setting up your App


Since version 3, you will need to set the "allowSyntheticDefaultImports" compiler option to "true" in your host apps tsconfig.json. Omitting this option will cause build errors in your app. This new requirement is related to a new dependency (vega-lite) which was added as part of our visualisation work.


The library requires the inclusion of a baseline set of CSS styles that it provides in the package under dist/genesys-webcomponents/genesys-webcomponents.css in apps that use the webcomponents. The stylesheet provides:
  • Baseline styles for browser elements
  • Classes for specific typography patterns
  • CSS variables for colors
  • CSS variables for spacing
  • CSS variables for z-index of "floating" non-flow content like menus, tooltips, popovers, or modals

The best mechanism for importing the stylesheet into your project will depend on how you handle CSS in your project in general. Reach out to the Common UI Development group if you're having trouble with your specific integration.
Note: Since v3 this baseline stylesheet is required.

Contextual z-index overrides

In complex layouts you may find that your app's use of z-index conflicts with the default z-index applied to raised content like dropdown menus, tooltips, popovers, or modals.
Components with layered content elements like menus or popovers use CSS variables for their z-index, and you can override the default z-index in your app's stylesheet for the specific context where you have a conflict.
.myApp .someElementThatHasContentWithCustomZIndexes {
  /* Provide higher z-index for dropdowns in this part of my app so they appear above the surrounding content */
  --gux-zindex-popup: 100;

Genesys Cloud applications

Genesys Cloud applications, or other always-online apps should import the library and call registerElements early during application bootstrap to register the components with the browser.
import { registerElements } from 'genesys-spark-components';

This will register the custom elements and automatically configure stencil to load icons and internationalization files from our CDN. You shouldn't need to bundle any additional assets into your application.


You will need to set a lang attribute on the a component or one of its ancestor elements to trigger localization. Normally, you should set it on the page somewhere at a high level, e.g. <html lang="en"> or <body lang="en"> and the components will localize based on that. If no language is set, the components default to English.

Framework Integration Notes

Development and Contribution

The common component library has a small set of developers, who also work on other projects, so contribution from users is welcome. If you need a new feature, the best way to get it is to work with the team to implement it yourself. Please reach out to discuss your work before opening a PR. An early conversation is the best way to avoid duplicated effort.
Also, be sure to read the Contributing Guidelines before starting development work.

Serving component and docs

Once you've checked out the project, install the local dependencies and start the dev server.
npm install

npm run dev

then navigate to http://localhost:8080/ to see the docs
If you want the docs to be accessible externally you can use
npm run dev.public

this will host the docs on This means they are available elsewhere on your network at http:/<your-ip-address>:8080/.

Running tests

npm run test

npm run

Documenting your component

Add an example.html file to your component's implementation directory with some examples.

Notes for external users

Currently this project is primarily use for internal Genesys projects, so most of our issue tracking and planning is done in internal tools. We do still look at GitHub isssues, but please understand that we're a small team and may not be able to address items right away, depending on internal priorities.