Meet peer dependency of @firebase/auth-interop-types

[strafe]

yarn insists that any peer dependencies of packages you depend upon yourself, must also be included in your own dependencies. If not it will print warnings.

Currently the @firebase/database package depends upon @firebase/auth-interop-types, which has a peer dependency on @firebase/app-types. However @firebase/app-types is set as a dev dependency rather than a regular one resulting in a warning when installing @firebase/database or any package that depends upon it (since I know it's an internal package).

$ yarn add firebase-admin
yarn add v1.22.10
info No lockfile found.
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning "firebase-admin > @firebase/database > @firebase/[email protected]" has unmet peer dependency "@firebase/[email protected]".
[4/4] 🔨  Building fresh packages...

This is quite annoying as projects that have a firebase-admin dependency get an unavoidable warning during installation (e.g. taskline) which can put users off.

---

This has come up previously in regards to the firebase package (#1207 & #1794) and was fixed by @Feiyang1 in #1807. However, firebase-admin is still facing this issue. It was reported in the firebase-admin repo (firebase/firebase-admin-node#973) but hasn't received any traction, possibly due to the fact the actual issue resides in this one.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 853a0de

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[strafe]

@googlebot I signed it!

[ryck]

It would be nice to have this resolved, I hate warnings on my logs :)

[hsubox76]

Fixing auth-interop-types here: #6940