#CREATE REACT APP YARN WORKSPACES HOW TO#

This is because when you add a dependency to say, the react-scripts package.json it will modify the yarn.lock in the root of the project. Note that there is only ONE yarn.lock file and that it resides in the root directory. This structure allows you to use npm or yarn to manage multiple dependencies and versions of each folder that you tell yarn is a workspace. other packages inside of create -react -app In the case of create-react-app that looks a bit like this: This means you can have packages with different dependencies and node binaries. Yarn workspaces are really just folders within your project that have their own package.json. # Use yarnįirstly, because react-scripts resides in a monorepo structure that uses yarn workspaces, I would recommended using yarn for your fork of react-scripts. I will try to tackle some of the key parts below, but really you should have a deep knowledge of yarn workspaces, npm modules and package.json.

#CREATE REACT APP YARN WORKSPACES HOW TO#

There are certain steps I will gloss over because they exist already in tutorials of how to fork react-scripts to your own npm module.

If you don't have to fork to a private repo, don't! Keep in mind that with the speed of development on react-scripts, whatever I describe might go out of date very quickly however.Īlso, I would just like to point out that the steps below are a lot of added work. This actually is possible, and below I will outline a way to go about this. your boss) you might be encouraged to fork it to a private repository instead.

Really, the best way to go about this is to fork react-scripts into your own npm module. This is often because you are using libraries that come with their own babel plugins (I'm looking at you, styled-components). If you use create-react-app, eventually you might reach a point where you want to modify the build scripts (aka webpack configs) yourself.

Create react app yarn workspaces