You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pkg-A is dependent of pkg-C which is not in the same monorepo.
pkg-C is dependent of pkg-B.
This means that when introducing changes to pkg-B, these changes are not tested during PR.
Only after a new version of pkg-B is released and is updated in pkg-C then I can suddenly see problem I could have avoided.
My solution is to force versions through root resolutions like so:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have the following monorepo:
pkg-A is dependent of pkg-C which is not in the same monorepo.
pkg-C is dependent of pkg-B.
This means that when introducing changes to pkg-B, these changes are not tested during PR.
Only after a new version of pkg-B is released and is updated in pkg-C then I can suddenly see problem I could have avoided.
My solution is to force versions through root resolutions like so:
It works for me, but is this a good practice?
Any suggestions how to deal with such problems (without changing pkg-C of course)
Beta Was this translation helpful? Give feedback.
All reactions