How to specify a specific version of a local package in a pnpm monorepo project?

Method for specifying local package version in pnpm monorepo project

When managing projects using pnpm and monorepo, it is often necessary to reference specific versions of other local packages in the subproject. For example, suppose there is a global component library called abcd that you want to use its version 1.0.0 in project1 . After using pnpm add abcd@1.0.0 --workspace command directly, the version displayed in package.json is "workspace:^" instead of the expected "workspace:1.0.0" . This is due to the default behavior of pnpm.

When pnpm is processing local packages, when adding dependencies using the --workspace flag by default, the version will be set to "workspace:^" to indicate that the latest version in the workspace that meets the range of ^ is used for easy management and updates.

But if you need to specify a specific version (such as 1.0.0), you can use two methods:

1. Manually modify the package.json file: After executing the pnpm add command, directly edit the package.json file of project1 , modify the abcd version from "workspace:^" to "workspace:1.0.0" , and then run pnpm install to update the dependency.

2. Use the --save-exact flag: When adding a dependency, use --save-exact flag to force the exact version number to be saved. For example, run pnpm add abcd@1.0.0 --workspace --save-exact . This way, the version in package.json will appear as "workspace:1.0.0" .

Through the above method, you can accurately specify the local package version in the pnpm monorepo project to meet project needs.

The above is the detailed content of How to specify a specific version of a local package in a pnpm monorepo project?. For more information, please follow other related articles on the PHP Chinese website!