Zoltan Kochan

Right. But we can't fix issues in third party libs. The global store is still used. Even with hoisted linker

I am not confident this scenario is frequent enough to justify the syntax sugar.

If Red Hat Dependency Analytics only supports npm, how will this help at all?

I could not reproduce the bug. After running `pnpm add --save-dev --save-exac typescript@"$TS_VERSION"` was typescript added with an exact version to `package.json`?

The problem is not with the update command. The problem is with the add command, which added `typescript` with version range `>=5.4

> But I want it to be ">=5.4

@shellscape something must differ. It doesn't make sense that it works locally but fails in CI.

No, I did not look into it yet. Issues related to the install command are prioritised earlier. Also, this is related to peer dependencies resolution, which makes the complexity of...

Try to install node-gyp as well: ``` pnpm add [email protected] node-gyp ```

Maybe we could reuse our existing field. Doing something like this: ```json { "pnpm": { "patchedDependencies": { "[email protected]": "script:ts-patch install" } } } ``` This would run `ts-patch install` as...