move aws-xray-sdk-core to peer dependencies #23
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mdlavin
approved these changes
Jan 24, 2019
|
@Druotic I'll release a major version bump in a sec |
|
Releasing as 3.0.0 now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This caused an issue where I had to explicitly use
yarn upgrade @lifeomic/graphql-resolvers-xray-tracingbecause it was pulling in it's own (older) version of the sdk. Having this as a peer dependency will help ensure no unexpected versions are used. I also added it as a dev dependency so that local linking will work when developing against this project.