#Pnpm workspace monorepo how to#

#Pnpm workspace monorepo how to#

And since it's not a named command-line parameter, it's difficult know how to search for help: pnpm install -h doesn't explain it. If I polled random developers familiar with PNPM, and asked them what - means, they probably would have no idea. For a large repo, you would never want to affect on 'all' packages, because you probably don't even know what half the packages are. This scenario seems fairly unlikely - for a small repo, you can just run the PNPM command several times. ) in the root will install express as dependency in all workspace packages. Running pnpm install -r express (or pnpm install express. This is generally a better approach than organizing it to reflect the implementation details that are happening behind the scenes.ģ. There is a scenario where the docker deployment wanted PNPM to locally install a single package (by copying its dependencies), but this is a somewhat special case, and it again would be invoked by an automated script.Īgreed, I would suggest for the spec to be organized around realistic problems a developer would encounter, and the list of commands they would run, with the goal to make those commands as simple and intuitive as possible. Instead, we would use a wrapper such as rush install -version-policy X which invokes PNPM behind the scenes with the right list of packages to install. However PNPM doesn't know what the meaningful subsets are, and the person isn't going to want to explain that using the PNPM command-line. In some cases it might be useful to install a subset of projects. It wouldn't make any sense, because nearly all our projects depend on the current (unpublished) versions of other projects in the repo.

In our monorepos, normally nobody would ever want to install a single project in isolation.

) in libs/ directory will only install dependencies of lib-a and lib-b Running pnpm install -r (or pnpm install.) in the root will install dependencies of all workspace packages.

Running pnpm install in the root will only create node_modules for the root package.json.