-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Add Yarn dedupe CI check #12717
Add Yarn dedupe CI check #12717
Conversation
yarn.lock
Outdated
version: 12.12.70 | ||
resolution: "@types/node@npm:12.12.70" | ||
checksum: 69c193e0bce8fa914d478f829bd923ee662b220e069a2e00ffbe109f27d0b38fbf2a9fe78c99eb4d4ccb294248ff8de68019a2c7fadb032d301c6feca25f3d22 | ||
"@types/node@npm:*, @types/node@npm:^17.0.5": |
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.
*
should refer to 12 still (we want that to be the version used in the repo)
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.
could we add a resolution entry in package.json to make @types/node always resolve to v12? is this a good idea?
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.
now * is resolved to v17, so typescript is failing to compile.
BTW, will we drop node v12 support when node v12 reaches the end of life at the end of the month? @SimenB |
Nah, will keep it until at least this summer when 17 is eol |
do you mean the node 17 support? but what I ask is node 12's support |
Yeah, we'll be keeping 12 at least as long as 17 |
@SimenB ci is happy. please take a look again. |
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.
Thanks!
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
Add a CI check yarn duplicate.
Test plan
Green CI