Advanced React APIs is a workshop repository, not a library

What the repository actually is

The single most useful thing to establish about advanced-react-apis is that it is not a component library, not a hook package, and not something you add to your dependencies. It is a workshop repository. The description field says Learn Advanced React Hooks workshop, and the topic list is workshop-shaped rather than library-shaped: epicreact-dev, epicweb-dev, hooks, kcd-edu, react and workshop.

It belongs to Epic Web Dev, the education company behind EpicReact.dev, and the deployed version is linked from the README at advanced-apis.epicreact.dev. The homepage recorded in the repository metadata points at that same deployed workshop, which tells you the site and the repository are two views of one course: the site runs the exercises, the repository holds them.

The README describes the subject matter in plain terms. It says the workshop looks at the more advanced hooks and APIs, and at ways they can be used to optimize components and custom hooks, and that each API is considered with the common use cases you run into in real applications. That framing matters, because it positions the material around use cases rather than around a list of API signatures.

The repository has roughly 2,100 stars and 1,270 forks. That fork count is unusually high relative to the star count for a private package, and it makes sense once you know what people are forking: they are forking to work through the exercises, not to depend on the code.

private true and a GPL licence tell you the rules

Two fields in the package.json settle the licensing and reuse question before you read a single exercise.

The first is the private flag set to true. That means the package is not published to a registry. You cannot install it from npm, and any attempt to treat it as a dependency will fail.

The second is the licence field, which reads GPL-3.0-only. The README carries a matching GPL 3.0 licence badge, and a LICENSE.md file at the root. Repository metadata records the licence as NOASSERTION, which is what the GitHub API returns when it cannot classify the licence automatically, so the package.json is the more precise source.

GPL-3.0-only on course material is a defensible choice, and it is the opposite of what you want from a library. If you were planning to lift code out of this repository into a proprietary application, the licence says stop. What the workshop is for is to read, run and solve.

The author field names Kent C. Dodds with an email address and a personal site, and the epicshop block repeats the same person as the instructor with an avatar path and a social handle. The instructor is not an anonymous maintainer; it is one named person, which is also the norm for the whole Epic Web workshop catalogue.

Prerequisites are stated as a short list of hooks

The README states the prerequisites in one line: you should be experienced with useState, useEffect and useRef. There is no list of earlier workshops and no required reading beyond that.

What the README does provide is a pre-workshop resources section, which is the more useful part. It links to four pieces of writing: an article on whether to use useState or useReducer, an article on how to implement useState with useReducer, an article comparing useEffect with useLayoutEffect, and an article on imperative versus declarative programming. All four are hosted by Kent C. Dodds except the last, which is hosted by ui.dev.

That reading list is a decent signal about the workshop's level. Two of the four entries are about choosing between state management approaches and about reimplementing one hook in terms of another. If those articles are familiar, the workshop is pitched correctly; if they are not, the first exercise is likely to land on unfamiliar ground.

System requirements and the three commands that verify them

The system requirements are explicit: git at version 2.18 or greater, NodeJS at version 20 or greater, and npm at version 8 or greater, with all of them available in your PATH. The README then gives you the verification command.

git --version
node --version
npm --version

If any of the three fail, the README points at instructions for fixing the PATH environment variable, with separate links for Windows and for macOS and Linux. That is a small thing to include and a useful thing, because a workshop that will not start is the most common way an otherwise good session gets lost in the first ten minutes.

The Node floor of 20 matters more than it looks. The package pins react and react-dom to exactly 19.0.0, with no range operator, so the workshop runs against one specific React version. A runtime older than the floor would not necessarily fail at install, but the pinned React 19 behaviour the exercises depend on is what the material was written against.

The epicshop CLI does the setup, and it is the actual entry point

Setup is one command.

```sh nonumber npx --yes epicshop@latest add advanced-react-apis

The --yes flag matters. It suppresses the install confirmation prompt so the command runs unattended, and the @latest tag means you get the current CLI rather than a pinned one. The add subcommand takes a workshop identifier, and advanced-react-apis is that identifier, matching the repository name and the slug in the epicshop product block.

If the command errors, the README asks you to open an issue with as many details as you can offer. That instruction tells you the maintainers expect this step to fail sometimes, which is a good reason to run it before the session rather than during it.

Once setup finishes, the app starts with a single command.

npm start ```

Note that this is not a Vite command and not a Next command. The script in package.json is pkgmgrx with a prefix pointing at the epicshop directory, running epicshop start. The CLI is therefore not only the setup tool, it is also the runtime that serves the workshop app.

What the scripts and directories are for

The package.json is short enough to read in full, and it explains how the workshop is wired.

The module setup is modern. The package declares type as module and an imports map where the pattern for #* resolves to ./*, which is the Node subpath imports feature used so exercises can import local files through package-name-like specifiers. The prettier config comes from a shared @epic-web/config package, so formatting is consistent across the whole workshop catalogue rather than hand-rolled per repository.

The scripts split into four groups. Setup comes in two flavours: a setup script that delegates to pkgmgrx, and a setup:custom script that runs a local setup-custom.js file in the epicshop directory. Running comes in two flavours that do the same thing: start and dev both run the epicshop start command. Quality comes in three: lint via eslint, format via prettier, and typecheck via tsc -b. There is also a postinstall script that changes into the epicshop directory and runs the package manager there, which is how the CLI installs its own dependencies.

The directory layout matches. exercises/ is where the workshop problems live. shared/ holds utilities reused across those exercises, which explains why @epic-web/workshop-utils appears in devDependencies. epicshop/ contains the CLI itself, including the custom setup script. public/ is static assets. Then there is configuration at the root: an eslint.config.js in flat config format, a tsconfig.json, a reset.d.ts for type definitions, a package-lock.json and an .npmrc.

The presence of a package-lock.json next to an .npmrc, in a repository whose scripts call a package manager abstraction rather than npm directly, is the clearest hint that this repository is not intended to be developed in isolation. It is intended to be scaffolded by the CLI, in whatever configuration the workshop tooling decides.

How to treat this repository after the workshop

Two structural facts shape what happens next. The first is that there are no releases. The releases list for this repository is empty, so there is no version to pin to, no changelog to read and no upgrade path to follow. The last recorded push is in early September 2026, so the material is being maintained, but maintenance here means keeping the workshop current against a moving React release rather than cutting versions.

The second is the product metadata. The epicshop block names the host as www.epicreact.dev, the slug as advanced-react-apis, and the display names EpicReact.dev and Epic React. It also carries a Discord channel id and two Discord tag ids, plus an onboarding video pointing at a getting-started guide for the Epic workshop app. Those fields are how the CLI and the site agree on where this workshop belongs in a larger course catalogue.

The practical upshot is that this repository is a course artifact with a maintenance schedule, not a dependency with a compatibility promise. Read it, fork it, work through it. If you later need React hooks for production code, reach for the React documentation rather than for the exercise solutions.

Editorial conclusion

The next concrete step is to run npx --yes epicshop@latest add advanced-react-apis and then inspect the exercises directory it populates: because the repository ships no releases and marks itself private, that scaffolded exercise tree is the actual workshop material, and everything else in the repository exists to run it.

Frequently asked questions

Official sources

1. epicweb-dev/advanced-react-apis on GitHub
2. Issues
3. Project website
4. README