-
Notifications
You must be signed in to change notification settings - Fork 71
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
chore: flip common deps in CLI to peer instead of regular dependencies #520
Conversation
"amplify-util-headless-input": "^1.9.5", | ||
"amplify-headless-interface": "^1.15.0" |
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.
amplify-headless-interface
should be a dev dep and amplify-util-headless-input
should be a peer dep
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.
Let me test that, when I'd had amplify-util-headless-input as a peer dep previously I'd had some build errors for types not found from that lib, and when adding to both peer and dev dep still wasn't seeing it work.
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 moved these both to peer deps, and added headless-input to dev-deps as well, since we were failing finding the types withouth.
1954967
b3936a2
to
1954967
Compare
1954967
to
0f8ad52
Compare
Codecov Report
@@ Coverage Diff @@
## main #520 +/- ##
=======================================
Coverage 62.61% 62.61%
=======================================
Files 276 276
Lines 17723 17723
Branches 4248 4248
=======================================
Hits 11098 11098
Misses 6047 6047
Partials 578 578 📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
Description of changes
flip common deps in CLI to peer instead of regular dependencies
this should protect us from some of the 'Feature Flags is not initialized' type errors we've seen, by ensuring the CLI uses it's own local version of the FeatureFlags lib.
Issue #, if available
N/A
Description of how you validated changes
yarn setup-dev
and then ran a few test commands w/amplify-dev api gql-compile
Checklist
yarn test
passesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.