Summary

Hi,

We ran into an issue where a package from the monorepo uses it's devDependency version instead of the dependency version from the app.

Scenario;
package X has react-hook-form as a peerDependency (>= 7) & as a devDependency (^7.54.1)
app A uses package X and has react-hook-form@7.55.0 installed, but it seems that the dependency references to the devDependency (7.54.1) instead of the peer dependency from the app (7.55.0), thus resulting in some conflicts of parameters/types/etc.

Is this something on turbo's side or the package manager's side?

Additional information

yarn 1.22.22
turbo 2.4.4

Example

No response