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

Another thing that we need to do is add the generation of changelogs. How are we going to do that?

Simple, with commit messages! There is a tool named 

 that does exactly what it says. We can quickly set it up now:

After it's installed, we need to configure it. In order to do that we need to change our 

{
  "auto-changelog": {
    "commitLimit": false,
    "template": "keepachangelog"
  }
}

 removes the limit on maximum commits per release, and 

 format which is a changelogs specification (read more about it 

Why this exact format and why not default? The answer is because in the next publishing lesson, we will use a Github Action that will expect exactly this format.

 file with a line to remove the default tag version prefix of 

. This prevents our auto-changelog tool from generating changelog logs with 

 prefix, which will make them truly compatible with

---
title: How to Automatically Generate a React App Changelog
isPublicLesson: false
---

Another thing that we need to do is add the generation of changelogs. How are we going to do that?

Simple, with commit messages! There is a tool named `auto-changelog` that does exactly what it says. We can quickly set it up now:

`npm install -D auto-changelog`

After it's installed, we need to configure it. In order to do that we need to change our `package.json`, adding these lines:

```json
{
  "auto-changelog": {
    "commitLimit": false,
    "template": "keepachangelog"
  }
}
```

`commitLimit` removes the limit on maximum commits per release, and `template` tells the tool to use `keepachangelog` format which is a changelogs specification (read more about it [here](https://keepachangelog.com/en/1.0.0/)).

Why this exact format and why not default? The answer is because in the next publishing lesson, we will use a Github Action that will expect exactly this format.

Another thing we need to do is add a `.npmrc` file with a line to remove the default tag version prefix of `v`, like this:

    tag-version-prefix=""

This means we will get `0.0.1` rather than `v0.0.1`. This prevents our auto-changelog tool from generating changelog logs with `v` prefix, which will make them truly compatible with
`keepachangelog` format.

Good. The last change to our `package.json` will be in the `scripts` section.

```json
{
  "scripts": {
    "preversion": "npm run clean && npm run build && npm run test",
    "version": "auto-changelog -p && git add CHANGELOG.md",
    "postversion": "git push && git push --tags"
  }
}
```

There's a lot going on here! Let me explain.

In order to bump up the version of our library we use `npm version` script. This script will take a parameter that may look like `minor`, `major`, `prerelease` etc.

We're going to run the following: `npm --no-git-tag-version version prerelease`.

We need the `--no-git-tag-version` flag to tell the `npm version` script: