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
Having warnings hanging around when working conditions to ignore them and not see some new issue. Hence I try keep them as clear as possible, especially when it comes to peer dependency issues.
The warning I receive with yarn and not solvable in root project, because the issue is in @remix-run/node. It has a dependency on @remix-run/server-runtime, which in turn has a peer dependency on react and react-dom. So @remix-run/node needs to provide the peer, OR if it does not want to, it needs to delegate the peer further, which it does not.
Anything speaking against doing the delegation to eliminate the warning? Again: having the peers resolved in root package/project does not eliminate the message because the peer is not delegated by @remix-run/node
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
-
Having warnings hanging around when working conditions to ignore them and not see some new issue. Hence I try keep them as clear as possible, especially when it comes to peer dependency issues.
The warning I receive with yarn and not solvable in root project, because the issue is in
@remix-run/node
. It has a dependency on@remix-run/server-runtime
, which in turn has a peer dependency onreact
andreact-dom
. So@remix-run/node
needs to provide the peer, OR if it does not want to, it needs to delegate the peer further, which it does not.Anything speaking against doing the delegation to eliminate the warning? Again: having the peers resolved in root package/project does not eliminate the message because the peer is not delegated by
@remix-run/node
Beta Was this translation helpful? Give feedback.
All reactions