Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unmet Peer Dependency Warnings #97

Open
AmanMulani opened this issue Apr 12, 2022 · 0 comments
Open

Unmet Peer Dependency Warnings #97

AmanMulani opened this issue Apr 12, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@AmanMulani
Copy link

Description

Whenever the yarn command is used to install dependencies for projects consisting of packages from the config repo, an array of warnings are seen, most of which are Unmet Peer Dependency Warning.
As per my understanding, this behavior is the result of the mismatch of peer-dependencies mentioned in the official babel packages and the versions that we have used inside our packages under the config repo.
For example:
medly/babel-config-react has @babel/plugin-transform-react-jsx and medly/babel-config (configs/packages/babel-config) in their dependencies. When we look into the package.json of babel-config, we have "@babel/core": "^7.14.5" as one of its dependencies. However, @babel/plugin-transform-react-jsx has a peer dependency of "@babel/core": "^7.0.0-0".
This dependency conflict might be the cause of the warnings.

To Reproduce

Steps to reproduce the behavior:

  1. Clone the Satellite Repo
  2. In the terminal, use the following command: yarn

Expected behavior

No warnings should be given for config-related packages.

Screenshots

image

@AmanMulani AmanMulani added the bug Something isn't working label Apr 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant