Part of making utilization of Booster components effortless is packaging our components into two bundles that you can quickly embed in your application. The recommended way to use our components is to embed the bundles via the Zywave CDN, but you can also install them via Yarn or NPM for a more à la carte experience.
Another advantage to loading these bundles via a CDN that can resolve npm tags is it allows us to push fixes/enhancements to your application without any deployment on your end.
Determine if your application requires stable third-party components
- If yes, get the most recent stable versions here:
- Booster Design System (ZUI) bundle: https://cdn.zywave.com/@zywave/zui-bundle@latest/dist/
- Booster Application Framework (ZAPI) bundle: https://cdn.zywave.com/@zywave/zywave-api-toolkit-bundle@latest/dist/
- If no, get the most recent pre-released versions here:
- Booster Design System (ZUI) bundle: https://cdn.zywave.com/@zywave/zui-bundle@next/dist/
- Booster Application Framework (ZAPI) bundle: https://cdn.zywave.com/@zywave/zywave-api-toolkit-bundle@next/dist/
Booster Design System (ZUI) bundle
Gain access to the Booster Design System—commonly known as the Zywave User Interface (ZUI)—components and stylesheets without having to install a single package.
Required files
There are three required files in order for the Booster Design System bundle to work properly in every application:
zui-bundle.fouc.css
- required for a smooth transition while all the scripts on the page loads, especially for non-SPAszui-bundle.app.css
- required for resetting styles for all base elements in your applicationbundle.js
* - required to load most ZUI components** properly
<link rel="stylesheet" href="https://cdn.zywave.com/@zywave/zui-bundle@{latest|next}/dist/css/zui-bundle.fouc.css" />
<link rel="stylesheet" href="https://cdn.zywave.com/@zywave/zui-bundle@{latest|next}/dist/css/zui-bundle.app.css" />
<script type="module" src="https://cdn.zywave.com/@zywave/zui-bundle@{latest|next}/dist/bundle.js"></script>
bundle.js
file is delivered as ES modules and must be loaded from other ES modules, e.g. <script type="module" src="https://cdn.zywave.com/@zywave/zui-bundle@latest/dist/bundle.js"></script>
.
** There are some exceptions to what components are part of the ZUI bundle. For example, <zui-table>
must be embedded separately. Learn more by visiting the Tables documentation.
Install via CDN
<!doctype html>
<html>
<head>
<title>Installing packages | Booster Development Network</title>
<!-- These two stylesheets should always be listed before all other application styles -->
<!-- Make sure `zui-bundle.fouc.css` is always listed first to counter FOUC -->
<link rel="stylesheet" href="https://cdn.zywave.com/@zywave/zui-bundle@{latest|next}/dist/css/zui-bundle.fouc.css" />
<link rel="stylesheet" href="https://cdn.zywave.com/@zywave/zui-bundle@{latest|next}/dist/css/zui-bundle.app.css" />
<script type="module" src="https://cdn.zywave.com/@zywave/zui-bundle@{latest|next}/dist/bundle.js"></script>
</head>
<body>
<!-- your content here -->
<body>
</html>
Install via Yarn/NPM
If you want an à la carte experience, you can install individual ZUI component packages via Yarn or NPM.
The following works with no extra work:
> yarn add @zywave/zui-components-all
> npm install @zywave/zui-components-all
Booster Application Framework (ZAPI) bundle
We also offer a bundle with all of the core componentry for the Booster Applicaton Framework—commonly known as the Zywave API Toolkit (ZAPI)—which includes the Zywave Shell, the API proxy, and more.
Required files
There are four required files in order for the Booster Application Framework bundle to work propertly in every application:
zui-bundle.fouc.css
- required for a smooth transition while all the scripts on the page loads, especially for Internet Explorer 11zui-bundle.app.css
- required for resetting styles for all base elements in your application- zui-bundle's
bundle.js
* - required to load most ZUI components properly - zywave-api-toolkit-bundle's
bundle.js
* - required to load all ZAPI components properly
<script type="module" src="https://cdn.zywave.com/@zywave/zywave-api-toolkit-bundle@{latest|next}/dist/bundle.js"></script>
bundle.js
files are delivered as ES modules and must be loaded from other ES modules, e.g. <script type="module" src="https://cdn.zywave.com/@zywave/zui-bundle@latest/dist/bundle.js"></script>
** There are some exceptions to what components are part of the ZUI bundle. For example, <zui-table>
must be embedded separately. Learn more by visiting the Tables documentation.
Install via CDN
<!doctype html>
<html>
<head>
<title>Installing packages | Booster Development Network</title>
<!-- These two stylesheets should always be listed before all other application styles -->
<!-- Make sure `zui-bundle.fouc.css` is always listed first to counter FOUC -->
<link rel="stylesheet" href="https://cdn.zywave.com/@zywave/zui-bundle@{latest|next}/dist/css/zui-bundle.fouc.css" />
<link rel="stylesheet" href="https://cdn.zywave.com/@zywave/zui-bundle@{latest|next}/dist/css/zui-bundle.app.css" />
<!-- It is required to also load the ZUI bundle and stylesheets above, especially for Zywave Shell usage -->
<script type="module" src="https://cdn.zywave.com/@zywave/zui-bundle@{latest|next}/dist/bundle.js"></script>
<script type="module" src="https://cdn.zywave.com/@zywave/zywave-api-toolkit-bundle@{latest|next}/dist/bundle.js"></script>
</head>
<body>
<!-- your content here -->
<body>
</html>
Install via Yarn/NPM
If you want an à la carte experience, you can install individual component packages via Yarn or NPM.
The following works with no extra work:
> yarn add @zywave/zui-components-all
> yarn add @zywave/zywave-components-all
> npm install @zywave/zui-components-all
> npm install @zywave/zywave-components-all
Where do I find a list of released packages to install?
- Search for
@zywave
at npmjs.com - Check out our Booster Design System monorepo and Booster Application Framework monorepo for all available packages
@latest and @next tags
You may have noticed in the code snippets above something like @latest
These terms correspond to npm distribution tags, where latest
is stable, production-ready code, and next
is generally unstable and not suitable to be referenced in a live environment.
These dist tags gives the toolkit the ability to deploy updates and fixes to your application, without you having to lift a finger!
Choose the right tag for your situation, and update accordingly (e.g., https://cdn.zywave.com/@zywave/zui-bundle@latest/dist/bundle.js
).
Version numbers
In addition to dist tags, you can use any valid npm version as found here.
This can be generally useful when a critical issue is encountered, or a deprecation notice goes unheeded.
A versioned URL could look something like the following:
https://cdn.zywave.com/@zywave/zywave-api-toolkit-bundle@1.0.22/dist/bundle.js