-
Notifications
You must be signed in to change notification settings - Fork 30
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
Track peer dependencies mismatches #6946
Conversation
this allows tracking of current peer dependencies mismatches for all three workspaces in the following issue: #6945
return new TextDecoder() | ||
.decode(rawOutput) | ||
.split('\n') | ||
.filter((line) => line.includes('has incorrect peer dependency')) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this will break if yarn output changes (or this project gets a new package manager) – what about using something like https://www.npmjs.com/package/validate-peer-dependencies?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that might be a good future improvement! I’m not massively interested in fixing straight away, as PNPM should make this unnecessary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’ve actually tried this package, but could not get it to work at all!
this seems to be reporting AR has having no peerdep issues, but when i run
|
Size Change: 0 B Total Size: 2.93 MB ℹ️ View Unchanged
|
Fixed in 0d08978 |
81cdcda
to
0badf78
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 This is great! Does it do any checking for the root package.json as well, or this not covered?
I don’t think it will because the “package” will not be identified. This can be improved upon, but a basic check seems better than nothing at all. |
What does this change?
This allows tracking of current peer dependencies mismatches for all three workspaces in the following issue: #6945
Why?
A small step in gaining visibility over peer dependencies mistmaches.
Prompted by the recent bump to React 18 in #6787
Tested
I triggered a workflow which resulted in a successful run!