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
During the linking of dependencies step, there is a warning about unmet peer dependency warning " > @babel/[email protected]" has unmet peer dependency "@babel/core@>=7.11.0"
What is the expected behavior?
The warning shouldn't be produced
Do you have any screenshots?
The text was updated successfully, but these errors were encountered:
Since no one picked this one up i would like to do it. Planning to share the screen with some CCI members while quickly fixing it + go over the tooling a bit.
Just to clarify, should we just add the missing dependency manually yarn add ?
What would be the procedure for updating the Changelog on adding the new package (like i assume we'll do in this case). Currently I'm thinking to add a line to the Fixes about the work done, and then duplicate it as 'adds package X' in Dependencies
What is the bug?
During the linking of dependencies step, there is a warning about unmet peer dependency
warning " > @babel/[email protected]" has unmet peer dependency "@babel/core@>=7.11.0"
What is the expected behavior?
The warning shouldn't be produced
Do you have any screenshots?
The text was updated successfully, but these errors were encountered: