How to specify the version of the local package in pnpm and monorepo projects?

pnpm and local package version specification method in monorepo project

When managing multi-package projects using pnpm and monorepo, it is often necessary to share local packages between projects. This article will explain in detail how to properly add and specify the local package version in pnpm and monorepo environments.

Suppose you have a global component called abcd and need to add its version 1.0.0 to a project named project1 . After using pnpm add abcd@1.0.0 --workspace command directly, the package.json file of project1 may show the version of "workspace:^" instead of the expected "workspace:1.0.0" . This is due to the default settings of pnpm.

The solution is as follows:

1. Use the --save-exact parameter: add --save-exact parameter to pnpm add command to force pnpm to write the exact version number. The command is as follows:

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

   This will ensure that the version in project1 's package.json file appears as "workspace:1.0.0" .

2. Modify the pnpm configuration file: Modify or create the .npmrc file in the root directory of the project and add the following configuration:

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

   After that, all pnpm add commands will be written to the exact version number by default.

3. Manually modify the package.json file: If the above method is invalid, you can manually edit the package.json file of project1 and modify "workspace:^" to "workspace:1.0.0" .

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

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