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
If we look at projects like react-redux, redux-actions or redux-promise we can notice that their are using peerDependencies for the redux-* dependencies.
I think we should follow this pattern because redux it self for example must be a direct dependency of the project which is using or implementing these libs. It's more easy to know what dependencies the project has, but at the same time removes some kind of abstractions which could help legibility.
Should we move redux, redux-actions and redux-promise to peerDependencies?
The text was updated successfully, but these errors were encountered:
If we look at projects like
react-redux
,redux-actions
orredux-promise
we can notice that their are using peerDependencies for theredux-*
dependencies.I think we should follow this pattern because
redux
it self for example must be a direct dependency of the project which is using or implementing these libs. It's more easy to know what dependencies the project has, but at the same time removes some kind of abstractions which could help legibility.Should we move
redux
,redux-actions
andredux-promise
to peerDependencies?The text was updated successfully, but these errors were encountered: