-
-
Notifications
You must be signed in to change notification settings - Fork 58
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 resolutions #259
Add yarn resolutions #259
Conversation
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 for working on this! This looks good to me, and I believe that the current CI failures are unrelated but we still need to get master green before landing....
This PR adds resolution support for ember-try configs that are using yarn. It uses the same merging strategy that the dependencies, devDependencies, and peerDependencies use.
94710c9
to
6a08b29
Compare
Codecov Report
@@ Coverage Diff @@
## master #259 +/- ##
==========================================
+ Coverage 95.36% 95.37% +0.01%
==========================================
Files 17 17
Lines 539 541 +2
==========================================
+ Hits 514 516 +2
Misses 25 25
Continue to review full report at Codecov.
|
1 similar comment
Codecov Report
@@ Coverage Diff @@
## master #259 +/- ##
==========================================
+ Coverage 95.36% 95.37% +0.01%
==========================================
Files 17 17
Lines 539 541 +2
==========================================
+ Hits 514 516 +2
Misses 25 25
Continue to review full report at Codecov.
|
Ok great! I just rebased off master and everything is green. |
Thanks! |
Upgrade ember-try to support `resolutions`. See ember-cli/ember-try#259
Needs to update ember-try to support `resolutions` See ember-cli/ember-try#259
@ryanto Would you be willing to add some documentation for this to the README? |
This PR adds resolution support for ember-try configs that are using yarn.
It uses the same merging strategy that the dependencies, devDependencies, and
peerDependencies use.