-
Notifications
You must be signed in to change notification settings - Fork 889
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
remove @firebase/app and @firebase/app-types from peerDependencies #2082
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.
Looks reasonable, but I had a couple of questions.
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.
Code change LGTM. Any idea why the CI has failed?
@schmidt-sebastian WDYT |
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.
LGTM
This is to solve the unmet
peerDependency
warning when@firebase/database
is used in Admin SDK. firebase/firebase-admin-node#614@firebase/app
was intentionally removed from Admin SDK's dependency to solve a version conflict issue when it's used together with JS SDK. #1916Though this PR is not the most correct way to solve the issue, it is quick and easy with little impact on user experience. The only user experience change is that user won't get unmet peer dependency warnings if
@firebase/database
is installed without installing@firebase/app
.It should be a rare case as we ask user to install
firebase
package in all our guides, which automatically includes@firebase/app
.The alternative solution is create a separate npm package for admin sdk consumption. It feels like an overkill and adds a lot of maintenance burden on us for little benefit.