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
I've got e.g. packages/web-project , packages/mobile-app and packages/shared/{web,mobile}.
The shared workspace contains both shared code that is used for both web and native but also for native-only. Now, when shared code requires a native-only third party package I list this package as peerDependency in the shared workspace. But this results in warnings from Yarn with the web-only workspaces. These web-only workspaces will now complain that the native-only third party package dependency is not met.
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
Uh oh!
There was an error while loading. Please reload this page.
-
I've got e.g. packages/web-project , packages/mobile-app and packages/shared/{web,mobile}.
The shared workspace contains both shared code that is used for both web and native but also for native-only. Now, when shared code requires a native-only third party package I list this package as peerDependency in the shared workspace. But this results in warnings from Yarn with the web-only workspaces. These web-only workspaces will now complain that the native-only third party package dependency is not met.
What is the correct way to deal with this?
I'm using the yarn 4.9.2.
Beta Was this translation helpful? Give feedback.
All reactions