-
Notifications
You must be signed in to change notification settings - Fork 30
Peer dependencies mismatch #6945
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
Labels
DCR Dependency
Dependency for DCR project
Dependencies
Pull requests that update a dependency file
dotcom-rendering
Epic
Milestone
Comments
mxdvl
added a commit
that referenced
this issue
Jan 12, 2023
this allows tracking of current peer dependencies mismatches for all three workspaces in the following issue: #6945
This was referenced Dec 14, 2023
Output from running
|
This was referenced Apr 22, 2024
dotcom-rendering
├─┬ @guardian/braze-components 18.1.0
│ ├── ✕ unmet peer @guardian/source-react-components@^18.0.0: found 22.0.1
│ └── ✕ unmet peer @guardian/source-react-components-development-kitchen@^16.0.0: found 19.0.0
├─┬ @guardian/commercial 17.12.0
│ └── ✕ unmet peer @guardian/support-dotcom-components@^1.0.7: found 2.1.0
└─┬ @storybook/react-webpack5 7.6.17
└─┬ @storybook/preset-react-webpack 7.6.17
└─┬ @pmmmwh/react-refresh-webpack-plugin 0.5.11
└── ✕ unmet peer webpack-dev-server@"3.x || 4.x": found 5.0.4 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
DCR Dependency
Dependency for DCR project
Dependencies
Pull requests that update a dependency file
dotcom-rendering
Epic
Uh oh!
There was an error while loading. Please reload this page.
Current peer dependencies mismatch
We want to enforce met peer dependencies for
@guardian/*
packagesThe text was updated successfully, but these errors were encountered: