What is a JavaScript workspace?

A workspace is a set of packages managed together in one repository so they share a single node_modules install and can depend on each other by name. The package manager symlinks local packages and hoists shared dependencies to the root.

Where does each config file go?

For npm and Yarn the workspaces field lives in the root package.json. For pnpm it goes in a separate pnpm-workspace.yaml at the repo root. In all cases the file sits at the top level of your monorepo.

What does nohoist do in Yarn?

By default Yarn hoists shared dependencies to the root node_modules. nohoist forces matching packages to stay inside each workspace's own node_modules, which is needed for tools like React Native that resolve binaries relative to the package.

Why is private set to true?

The root package of a workspace must be marked private so it is never accidentally published to a registry. npm and Yarn refuse to enable workspaces unless the root package.json has private: true.

Can I use nested glob patterns?

Yes. Globs like packages/* match direct children, while packages/** matches any depth. Most monorepos keep one level such as packages/* and apps/* for clarity, but deeper patterns are valid if your layout needs them.

npm/Yarn/pnpm Workspaces Config Builder

Email me this result

Get this tool's output sent to your inbox, plus one useful tool a week. No spam, unsubscribe any time.

Set up a JavaScript monorepo

A monorepo holds many packages in one repository. Workspaces are the native feature in npm, Yarn, and pnpm that wires those packages together: they share one install, link local packages by name, and let you run scripts across the whole tree. This builder produces the exact workspace declaration for whichever manager you use.

How it works

For npm and Yarn, the configuration lives in the root package.json under a workspaces key. The simplest form is an array of glob patterns — each glob points at folders that each contain a package.json. Yarn additionally supports an object form with a nohoist array to keep certain dependencies inside individual packages instead of hoisting them to the root.

For pnpm, the configuration is a separate pnpm-workspace.yaml file with a packages list of the same glob patterns. pnpm reads this file to discover workspace members and create its content-addressable, symlinked node_modules.

The patterns are evaluated relative to the repo root. A glob like packages/* matches every immediate subfolder of packages. Each matched folder must contain its own package.json with a unique name, which becomes the import name other packages use.

Tips and notes

Mark the root package private: true — all three managers require it for workspaces.
Keep package names unique; that name is how sibling packages reference each other.
Use nohoist (Yarn) only when a tool breaks under hoisting, such as React Native.
After editing the config, run a fresh install so symlinks are created.