Course overview

How to work with course materials

Introduction

Setting up Developer Environment

Setting up Initial Project

How to Use ESLint and Prettier Together in a React Project

How to Configure React to Use TypeScript

How to Add Jest to a React Project for Automated Testing

Setting up developer environment

Building React Hooks: API Considerations and Best Practices

How to Implement a Custom useBoolean React Hook

Testing a Custom useBoolean Hook With React Testing Library

How to Implement a Custom useMap Hook With Tests

How to Quickly Import Custom React Hooks With an Index File

Implement an Object Returning API With a react-hanger Clone

Development of custom hooks

CommonJS vs ES6: An Intro to JavaScript Module Systems

What is Transpilation? An Intro to Transpilers vs Compilers

An Intro to Transpilers: ESBuild, Babel, and SWC Compared

What are Babel Transforms and Plugins?

A Beginner's Guide to JavaScript Bundlers

How to Simplify Bundling React Code With Microbundle

How to Add TypeScript Build Steps to React

How to Implement Babel Build Steps in a React App

Conclusion

Preparing code for publishing

Add Continuous Integration to a React Build With GitHub Actions

How to Automatically Generate a React App Changelog

How to Publish a React Library to NPM With GitHub Actions

Publishing the Code

In this course we’ll build a set of custom reusable hooks, a mini react-hanger clone, essentially going from nothing to a fully-automated publishing pipeline that follows the best practices.  We will cover common Hooks APIs every React developer should know, then dive straight into implementing Custom React Hooks, similar to what you will find in leading React libraries in the open source React ecosystem.

## Why this course
React Hooks promise to eliminate the difficulties of sharing state without writing class-based components. The challenge is that Hooks do away with the lifecycle methods and class-based semantics of state management that many React developers were familiar with.  Learning React Hooks on your own can be time consuming, confusing and frustrating.  With that in mind, The newline Guide to Creating a React Hooks Library, was created to provide a complete tutorial that fully covers React Hooks.  Within a few hours you'll have a strong grasp on React Hooks and how to implement them.

## Course Topics
This course packs practical hands-on-instruction using and building React Hooks, along with the best practices you need to build wider React Hooks libraries others across your organization can use.
The first module provides an overview of the React Hooks library project we’ll build, and we'll set up a complete environment with tools for library development.
The subsequent modules then take you through building with React Hooks and creating your React Hooks library, including:
- Hooks API fundamentals
- Developing custom React Hooks
- How to write reusable React Hooks
- Common React Hooks mistakes to avoid in your code
- Transpilers and bundlers for JavaScript libraries
- Using GitHub Actions to test, build, and lint your library
- Publish your React Hooks library to NPM

We’ll use tools including React, TypeScript, Babel, as well as GitHub Actions to build, test, and package a React Hooks library available for others to download from NPM.  Ultimately, build your own React Hooks library and learn the best practices that will make your code reusable. With these skills, you can contribute more confidently to any React codebase using React Hooks, and make your team more productive.

This course is a complete step-by-step guide to coding custom React Hooks and building a Hooks library from scratch.  Confidently master React Hooks, a transformative update added since React version 16.8, that makes it much easier to reuse code as your React codebase grows.

The newline Guide to Creating a React Hooks Library

Common React Hooks mistakes to avoid in your code

Transpilers and bundlers for JavaScript libraries

Using GitHub Actions to test, build, and lint your library

. Continuous integration is a set of automated tasks or jobs that are run, usually triggered by some event in the repository. The goal of those tasks is usually to check whether functional tests are still green, and compilation has been successful.

Bear in mind that CI tasks are not limited to functional tests. They may check for other things such as whether code follows any format or naming conventions, or whether test coverage stays above its target percentage. It can also automatically publish your package, deploy your app and so on.

In other words, a CI service or platform gives you the ability to run any script on a set of triggers or events that help achieve some goal in a consistent and regular way.

This is a CI platform provided by GitHub. Its typical events include pushes into the repository, new pull requests, new tag pushed etc. The first workflow that we're going to implement will be a typical "run tests, run lint and check if it's all good" triggered by any push to the master or new pull request. If any of the jobs fail it means that the code is broken in some way and that it needs to be fixed before it can be merged into the master branch. If we wanted to push directly to the master where we have the rights, then at least we'll get notified that we've missed something.

So, to get our CI working with GHA, we need to create the folder 

name: Node.js CI

on:
  push:
    branches: [master]
  pull_request:
    branches: [master]

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v2
      - name: Use Node.js 12.x
        uses: actions/setup-node@v1
        with:
          node-version: 12.x
      - uses: actions/cache@v2
        with:
          path: node_modules
          key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
          restore-keys: |
            ${{ runner.os }}-node-
      - name: Install Dependencies
        run: npm install
      - name: Linting
        run: npm run lint
      - name: Testing
        run: npm run test
      - name: Building
        run: npm run build

Let me explain step-by-step what's happening here.

---
title: Add Continuous Integration to a React Build With GitHub Actions
isPublicLesson: false
---

The next thing to add is **continuous integration (CI)**, using **GitHub Actions (GHA)**. Continuous integration is a set of automated tasks or jobs that are run, usually triggered by some event in the repository. The goal of those tasks is usually to check whether functional tests are still green, and compilation has been successful.

Bear in mind that CI tasks are not limited to functional tests. They may check for other things such as whether code follows any format or naming conventions, or whether test coverage stays above its target percentage. It can also automatically publish your package, deploy your app and so on.

In other words, a CI service or platform gives you the ability to run any script on a set of triggers or events that help achieve some goal in a consistent and regular way.

Let's take a look at GitHub Actions.

This is a CI platform provided by GitHub. Its typical events include pushes into the repository, new pull requests, new tag pushed etc. The first workflow that we're going to implement will be a typical "run tests, run lint and check if it's all good" triggered by any push to the master or new pull request. If any of the jobs fail it means that the code is broken in some way and that it needs to be fixed before it can be merged into the master branch. If we wanted to push directly to the master where we have the rights, then at least we'll get notified that we've missed something.

So, to get our CI working with GHA, we need to create the folder `.github/workflows` and then the file `ci.yml` inside it, and paste in this code:

```yaml
name: Node.js CI

on:
  push:
    branches: [master]
  pull_request:
    branches: [master]

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v2
      - name: Use Node.js 12.x
        uses: actions/setup-node@v1
        with:
          node-version: 12.x
      - uses: actions/cache@v2
        with:
          path: node_modules
          key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
          restore-keys: |
            ${{ runner.os }}-node-
      - name: Install Dependencies
        run: npm install
      - name: Linting
        run: npm run lint
      - name: Testing
        run: npm run test
      - name: Building
        run: npm run build
```