Closed g-chao closed 1 week ago
If you declare a workspace package in peerDependencies, though you put the version range there, PNPM does not respect it. Below is an example: peerDependencies section in @rushstack/heft-api-extractor-plugin project package.json
@rushstack/heft-api-extractor-plugin
"peerDependencies": { "@rushstack/heft": "0.66.18" },
The actual pnpm-lock.yaml
pnpm-lock.yaml
So, we don't need to take these packages into consideration when calculating packageJsonInjectedDependenciesHash.
Manually tested with Monorepo locally.
Summary
If you declare a workspace package in peerDependencies, though you put the version range there, PNPM does not respect it. Below is an example: peerDependencies section in
@rushstack/heft-api-extractor-plugin
project package.jsonThe actual![img_v3_02c8_154f1501-0d30-4138-a2ce-b5e78bf2775h](https://github.com/microsoft/rushstack/assets/10736839/681d7c50-7fe8-49af-828e-f76233a5a591)
pnpm-lock.yaml
So, we don't need to take these packages into consideration when calculating packageJsonInjectedDependenciesHash.
How it was tested
Manually tested with Monorepo locally.