add packages to dep list for peer dep requirement #1807
Merged
Conversation
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
@firebase/{component}has a peer dependency on@firebase/app-typesand some has peer dependency on@firebase/util.Since firebase depends on
@firebase/{component}directly, it should list all the peer dependencies from@firebase/{component}as its dependency, otherwise yarn will complain with unmet peer dependency warning.The fact that
@firebase/app-typesis a dependency of@firebase/appis not enough as explained in yarnpkg/yarn#5347 (comment)This is not a problem with npm because npm doesn't care how the peer dependencies are installed as long as they are there.