Package Exports

@ctoec/component-library

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@ctoec/component-library) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

CT OEC Component Library

This library provides a uniform collection of reusable UX components, static assets and functional units specific to the State of Connecticut's Office of Early Childhood.

Setup

Local

Install (if you haven't already) Visual Studio, Node 12 and Yarn.
Install all corresponding yarn dependencies, based on the static versions specified in yarn.lock:
```
yarn install --frozen-lockfile
```

Examples

If you're looking for some specific UX examples, we have a Storybook site deployed to GitHub Pages, showcasing all of the components within this library.

You can check it out live at http://ctoec.github.io/component-library/.

Deploying Storybook

These Storybook deployments are handled with the storybook-deployer package, using the gh-pages branch of this repository as the site's source. Additionally, all commits to our core base branch will trigger an associated GitHub Action that automatically updates our Storybook site. So it'll be kept up to date with the latest state of our library at all times!

Regardless, if there's ever a need for the site to be updated manually, the following command should be run from project root:

yarn run deploy-storybook

To use this library

yarn add @ctoec/component-library
Import the stylesheets in your application with import '@ctoec/component-library/dist/assets/styles/index.scss'
import { ComponentOfYourChoice } from @ctoec/component-library

Publishing

Increment version in package.json
yarn build
npm publish (If this is the first time, you will need to authenticate yourself by running npm login)