Firebase-admin-node: firebase-admin 8.3.0 causes npm install warnings

Created on 7 Aug 2019  路  4Comments  路  Source: firebase/firebase-admin-node

Describe your environment

  • Operating System version: Mac OS
  • firebase-admin SDK version: 8.3.0

Describe the problem

Running npm install with firebase-admin as a dependency results in the following warnings:

npm WARN @firebase/[email protected] requires a peer of @firebase/[email protected] but none is installed. You must install peer dependencies yourself.
npm WARN @firebase/[email protected] requires a peer of @firebase/[email protected] but none is installed. You must install peer dependencies yourself.
npm WARN @firebase/[email protected] requires a peer of @firebase/[email protected] but none is installed. You must install peer dependencies yourself.

I believe this is caused by this change in 8.3.0:

Downgraded the dependency on the @firebase/app package to a dev dependency.

Steps to reproduce:

Clone the functions-samples repo, navigate to the functions dir of big-ben, and run npm install [email protected]

database

Most helpful comment

I ran to get around it.
npm install @firebase/app
npm install @firebase/app-types

Then ran install npm install

All 4 comments

I found a few problems with this issue:

  • I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
  • This issue does not seem to follow the issue template. Make sure you provide all the required information.

Possible options under consideration:

  1. Remove the peer dependency
  2. Introduce a new database package specifically for this use case (@firebase/database-standalone)

I ran to get around it.
npm install @firebase/app
npm install @firebase/app-types

Then ran install npm install

Yes, this happened because we downgraded the dependency on @firebase/app to a dev dependency. The @firebase/database package is designed to work without @firebase/app, but it still declares a peer dependency on it. The JS SDK team (@Feiyang1 et al) are already on the case. In the meantime, you're free to ignore the warning. I don't think there are any negative consequences.

Was this page helpful?
0 / 5 - 0 ratings