Course Welcome

An Intro to Component Libraries and Design Systems

Syllabus

Environment setup

Introduction

Which React Components to Build? An Atomic Design Guide

Which UI Elements Should be Turned Into React Components?

Choose React Dependencies for a Maintainable Component Library

Shared components

How to Host an NPM Package in GitHub for Free

How to Add Storybook to React to Test Component Library Locally

How to Keep React Code Consistent With Prettier and ESLint

Library creation

Build a Custom React Button Component With forwardRef API

Build a Custom Design System With React Styled Components

Validate React Props With PropTypes and TypeScript

Shared component patterns

How to Design Compound Components With React Context

How to Design Custom React Field Components With useUniqueID

How to Extend Styled Component Styles With New Style Props

Advanced patterns

How to Test React Component Libraries With ts-jest

How to Build Tests For React Button Components

How to Build Accessibility Tests For React Field Components

Component testing

The Best Ways to Bundle React Modules Into Packages

Build process

Setting Up Continuous Integration for a React Component Library With GitHub Actions

Deployment and automation

This course will teach you how to create a flexible, private, enterprise-grade component library using React.

Since its introduction in 2013, React has become one of the [most used front-end frameworks](https://2019.stateofjs.com/front-end-frameworks/). Its component-based architecture and flexibility has made it the framework of choice for those needing to share code across multiple teams.

However, the same flexibility that has helped React grow in popularity also creates many challenges when creating shared assets and tooling. Some of the most commonly asked questions include:

- What components should be shared?
- How do I choose which dependencies to include in my library?
- Which component APIs and design patterns allow for the most flexibility?
- How do I document and build my components?
- How should I be testing my library?
- Where do I deploy my components for internal use?

This course will teach you how to create a flexible, private, enterprise-grade
component library using React.

The newline Guide to Building a Company Component Library

How to identify potential shared components in an existing codebase

Importance of choosing your libraries dependencies

How to create an NPM library from scratch with TypeScript and Storybook

Basic and advanced API patterns for shared components

How to build and deploy a modern NPM package to a private NPM registry

Now that our component library is building we have to find a secure way to publish our package. It's possible to lint, test, and publish our package locally, but this can be difficult to enforce with larger teams. In this module we will be automating our publish process in a CI/CD environment.

Since we are storing our repository within GitHub we will be using 

 as our private NPM registry. Both services have a generous free tier for open-source software as well as monthly credits for private packages. Everything we do in this module will stay within the limits of the free tier.

GitHub Actions runs workflows based on repository events. For our publish workflow we will only want to run if a new NPM version has been tagged in git (

To enable this workflow create a new file at 

mkdir -p .github/workflows
touch .github/workflows/publish.yml

# File: .github/workflows/publish.yml

name: Publish

on:
  push:
    tags:
      - 'v*'

jobs:
  publish:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2
    - uses: actions/setup-node@v1
      with:
        node-version: '16.x'
        registry-url: 'https://npm.pkg.github.com'
        scope: '@GITHUBUSERNAME'
    - run: npm ci
    - run: npm run lint
    - run: npm run test
    - run: npm run build
    - run: npm publish
      env:
        NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

 workflow will run whenever a new tag is pushed that matches the 

---
title: Setting Up Continuous Integration for a React Component Library With GitHub Actions
privateVideoUrl: https://fullstack.wistia.com/medias/yvua74wgb1
---

Now that our component library is building we have to find a secure way to publish our package. It's possible to lint, test, and publish our package locally, but this can be difficult to enforce with larger teams. In this module we will be automating our publish process in a CI/CD environment.

Since we are storing our repository within GitHub we will be using [GitHub Actions](https://github.com/features/actions) as the CI/CD environment and [GitHub Packages](https://github.com/features/packages) as our private NPM registry. Both services have a generous free tier for open-source software as well as monthly credits for private packages. Everything we do in this module will stay within the limits of the free tier.

## GitHub Actions configuration

GitHub Actions runs workflows based on repository events. For our publish workflow we will only want to run if a new NPM version has been tagged in git (`v1`, `v2`, etc.).

To enable this workflow create a new file at `.github/workflows/publish.yml`.

Learn

The newline Guide to Building Your First GraphQL Server with Node and TypeScript

Teach

Amelia Wattenberger

Author of Fullstack D3

Community

The newline Guide to Building a Company Component Library

Module 1: Introduction

Introduction:

Start Here

Introduction: (2:36)

Course Welcome

Introduction: (1:44)

An Intro to Component Libraries and Design Systems

Introduction: (1:23)

Syllabus

Introduction: (0:49)

Environment setup

Module 2: Shared components

Lesson 1: (2:04)

Which React Components to Build? An Atomic Design Guide

Lesson 2: (4:30)

Which UI Elements Should be Turned Into React Components?

Lesson 3: (2:22)

Choose React Dependencies for a Maintainable Component Library

Module 3: Library creation

Lesson 1: (4:37)

How to Host an NPM Package in GitHub for Free

Lesson 2: (4:46)

How to Add Storybook to React to Test Component Library Locally

Lesson 3: (4:55)

How to Keep React Code Consistent With Prettier and ESLint

Module 4: Shared component patterns

Lesson 1: (7:49)

Build a Custom React Button Component With forwardRef API

Lesson 2: (13:39)

Build a Custom Design System With React Styled Components

Lesson 3: (2:05)

Validate React Props With PropTypes and TypeScript

Module 5: Advanced patterns

Lesson 1: (2:09)

How to Design Compound Components With React Context

Lesson 2: (15:48)

How to Design Custom React Field Components With useUniqueID

Lesson 3: (7:51)

How to Extend Styled Component Styles With New Style Props

Module 6: Component testing

Lesson 1: (2:45)

How to Test React Component Libraries With ts-jest

Lesson 2: (5:13)

How to Build Tests For React Button Components

Lesson 3: (4:52)

How to Build Accessibility Tests For React Field Components

Module 7: Build process

Lesson 1: (2:55)

The Best Ways to Bundle React Modules Into Packages

Module 8: Deployment and automation

Lesson 1: (3:18)

Setting Up Continuous Integration for a React Component Library With GitHub Actions

Setting Up Continuous Integration for a React Component Library With GitHub Actions