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

The build process for a library has many similarities with applications. We want to take a single entry point, which contains our components, and bundle them together into an output file. When building applications, the target environment is a web browser. 

 is a popular module bundler that helps bundle a wide variety of assets into an output that browsers can understand.

For libraries the target environment is often another development environment, not a browser. This changes the type of assets we can produce and the tools required to build them. In this course we will be using 

Originally, there was no open standard for importing/exporting JavaScript modules. Over time there have been many formats developed which realize this, each with their own unique benefits. Some common formats include:

---
title: The Best Ways to Bundle React Modules Into Packages
privateVideoUrl: https://fullstack.wistia.com/medias/u7rc0usbax
---

The build process for a library has many similarities with applications. We want to take a single entry point, which contains our components, and bundle them together into an output file. When building applications, the target environment is a web browser. [Webpack](https://webpack.js.org/) is a popular module bundler that helps bundle a wide variety of assets into an output that browsers can understand.

For libraries the target environment is often another development environment, not a browser. This changes the type of assets we can produce and the tools required to build them. In this course we will be using [RollupJS](https://rollupjs.org/guide/en/) as our module bundler.

## Module formats

Originally, there was no open standard for importing/exporting JavaScript modules. Over time there have been many formats developed which realize this, each with their own unique benefits. Some common formats include:

-   **CommonJS (CJS)**

    -   The module system that Node.js has used historically
    -   Server-side only
    -   `require` and `module.exports`
-   **ESModules (ES)**

    -   The official specification for a [standard module system](https://hacks.mozilla.org/2018/03/es-modules-a-cartoon-deep-dive/)
    -   Can work in server and modern browser environments
    -   `import` and `export`
    -   _Supports tree-shaking_

Where are the rest of the lessons for this module?

Drewsup123

It looks like there is an issue on the Newline side of things relating to course publishing. I'll reach out to them to figure out why these lessons are missing.

Austin Green

Is there another resource where I can see these lessons?  Kind of feels like we're missing the crucial piece of building a component library with these missing :c

Charlie Wynn

Hi Charlie. I surfaced this issue to newline and haven't received word on when the publishing platform will be fixed. Can you please message them using the live-chat functionality on the site? They will be able to further assist there.

Looking at the course .zip folder - it looks like the nested directories for module-07 and module-08. lesson-07.undefined for example. And lesson-07 has sub-directories with lesson-06-02 under them. A bit strange..Maybe this is why newline can't pick up your videos? Not sure if you have a similar folder structure when you upload videos

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

The Best Ways to Bundle React Modules Into Packages