In pnpm and monorepo environments, how do I ensure that the version of the local package appears as a specific version rather than a floating version?

Precisely specify local package versions under pnpm and monorepo environments

When using pnpm and monorepo to manage projects, the version number of the local package is often inconsistent with expectations. For example, in monorepo, you want project1 to use the 1.0.0 version of the global component abcd , but after executing pnpm add abcd@1.0.0 --workspace , the version displayed in package.json is "workspace:^" instead of "workspace:1.0.0" . This is because pnpm uses floating versions to manage workspace dependencies by default, allowing automatic updates under the same major version number.

To ensure that the exact version number (for example 1.0.0) is displayed in package.json , add the package using the following command:

 pnpm add abcd@1.0.0 --save-exact --workspace

--save-exact parameter forces pnpm to use the exact version number instead of the floating version, thus displaying "workspace:1.0.0" in package.json .

Another way is to set the save-exact option globally. Add in ~/.npmrc or .npmrc file in the root directory of the project:

 <code>save-exact=true</code>

This setting will make all subsequently added dependencies use the exact version number.

Through the above methods, you can effectively control the version of local packages in pnpm and monorepo environments, ensuring the accuracy and consistency of project dependencies.

The above is the detailed content of In pnpm and monorepo environments, how do I ensure that the version of the local package appears as a specific version rather than a floating version?. For more information, please follow other related articles on the PHP Chinese website!