pnpm version: 7.5.1
modifying the package json and running pnpm install produces a different change in the lock than pnpm install package
Code to reproduce the issue:
Upgrade a package in a monorepo environment by editing the package.json manually, for example superagent:
@@ -765,7 +765,7 @@ importers:
stylelint-config-recommended: 2.1.0_stylelint@9.3.0
stylelint-config-styled-components: 0.1.1
stylelint-processor-styled-components: 1.10.0
- superagent: 3.8.2
+ superagent: 3.8.3
url-search-params-polyfill: 5.0.0
use-debounce: 3.0.1_react@16.9.0
webfontloader: 1.6.28
Expected behavior:
Only that package related stuff changes in the lock
Actual behavior:
Some unrelated stuff to the updated package is changing in the lock:
@@ -10036,7 +10036,6 @@ packages:
typescript: 4.6.3
transitivePeerDependencies:
- supports-color
- dev: false
/@typescript-eslint/eslint-plugin/5.18.0_xv2274wrqxbgrlpvs4tbjqmkuy:
resolution: {integrity: sha512-tzrmdGMJI/uii9/V6lurMo4/o+dMTKDH82LkNjhJ3adCW22YQydoRs5MwTiqxGF9CSYxPxQ7EYb4jLNlIs+E+A==}
@@ -17207,7 +17206,7 @@ packages:
eslint-plugin-import: ^2.14.0
dependencies:
eslint: 5.16.0
- eslint-plugin-import: 2.16.0_ergv4ifw2at7hzm2g6v4ssjyya
+ eslint-plugin-import: 2.16.0_eslint@5.16.0
eslint-restricted-globals: 0.1.1
object.assign: 4.1.2
object.entries: 1.1.5
@@ -17234,7 +17233,7 @@ packages:
dependencies:
eslint: 5.16.0
eslint-config-airbnb-base: 13.1.0_47jlxgemtojldybvvfisc7gfn4
- eslint-plugin-import: 2.16.0_ergv4ifw2at7hzm2g6v4ssjyya
+ eslint-plugin-import: 2.16.0_eslint@5.16.0
dev: true
/eslint-config-danbriggs5-base/1.0.0_q2xwze32dd33a2fc2qubwr4ie4:
@@ -17872,7 +17871,6 @@ packages:
transitivePeerDependencies:
- supports-color
- typescript
- dev: false
2 different unexpected changes:
- dev flags changing for unrelated packages
- eslint-plugin-import changing to a different reference in the lock, from
2.16.0_ergv4ifw2at7hzm2g6v4ssjyya to 2.16.0_eslint@5.16.0, checking the references in the lock, they contain the same data:
/eslint-plugin-import/2.16.0_ergv4ifw2at7hzm2g6v4ssjyya:
resolution: {integrity: sha512-z6oqWlf1x5GkHIFgrSvtmudnqM6Q60KM4KvpWi5ubonMjycLjndvd5+8VAZIsTlHC03djdgJuyKG6XO577px6A==}
engines: {node: '>=4'}
peerDependencies:
'@typescript-eslint/parser': '*'
eslint: 2.x - 5.x
peerDependenciesMeta:
'@typescript-eslint/parser':
optional: true
dependencies:
'@typescript-eslint/parser': 5.2.0_idyk4lcuu7e2besohrcqefwvfq
contains-path: 0.1.0
debug: 2.6.9
doctrine: 1.5.0
eslint: 5.16.0
eslint-import-resolver-node: 0.3.6
eslint-module-utils: 2.7.3_6wzttxhatm5d23hrj3myvcyrwy
has: 1.0.3
lodash: 4.17.21
minimatch: 3.1.2
read-pkg-up: 2.0.0
resolve: 1.22.1
transitivePeerDependencies:
- eslint-import-resolver-typescript
- eslint-import-resolver-webpack
- supports-color
dev: true
is the same as
/eslint-plugin-import/2.16.0_eslint@5.16.0:
resolution: {integrity: sha512-z6oqWlf1x5GkHIFgrSvtmudnqM6Q60KM4KvpWi5ubonMjycLjndvd5+8VAZIsTlHC03djdgJuyKG6XO577px6A==}
engines: {node: '>=4'}
peerDependencies:
'@typescript-eslint/parser': '*'
eslint: 2.x - 5.x
peerDependenciesMeta:
'@typescript-eslint/parser':
optional: true
dependencies:
contains-path: 0.1.0
debug: 2.6.9
doctrine: 1.5.0
eslint: 5.16.0
eslint-import-resolver-node: 0.3.6
eslint-module-utils: 2.7.3_ulu2225r2ychl26a37c6o2rfje
has: 1.0.3
lodash: 4.17.21
minimatch: 3.1.2
read-pkg-up: 2.0.0
resolve: 1.22.1
transitivePeerDependencies:
- eslint-import-resolver-typescript
- eslint-import-resolver-webpack
- supports-color
dev: true
Additional information:
node -v prints: v16.15.1- Windows, macOS, or Linux?: any OS
pnpm version: 7.5.1
modifying the package json and running
pnpm installproduces a different change in the lock thanpnpm install packageCode to reproduce the issue:
Upgrade a package in a monorepo environment by editing the package.json manually, for example superagent:
Expected behavior:
Only that package related stuff changes in the lock
Actual behavior:
Some unrelated stuff to the updated package is changing in the lock:
2 different unexpected changes:
2.16.0_ergv4ifw2at7hzm2g6v4ssjyyato2.16.0_eslint@5.16.0, checking the references in the lock, they contain the same data:is the same as
Additional information:
node -vprints: v16.15.1