-
Notifications
You must be signed in to change notification settings - Fork 373
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
13.0.0 can't be used with the latest firebase-functions release (npm error: Conflicting peer dependency) #2772
Comments
I found a few problems with this issue:
|
From what I can tell, this happened with the Looks like some sort of workflows need to be instituted by the Firebase team, so that you release both these packages (and related dependencies) together. Otherwise, upgrades such as dependabot workflows, or someone starting out right now, will run into this problem. |
This was fixed in latest patch release! https://github.com/firebase/firebase-functions/releases/tag/v6.1.1 Sorry for the delay. |
@taeold The latest versions of firebase-functions and firebase-admin don't work together
|
Right, this is not fixed yet, @taeold (thanks @simeon9696): Using the latest releases:
This is still failing:
Looks like And perhaps even more importantly, there needs to be a process (or not explicit major version dependency checks in |
not exactly a fix but a work around until this gets sorted for me was:
not sure if tough-cookie is needed for everyone but something to do with @types/request had an issue with it for me too |
@taeold can this be fixed soon? |
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
firebase-admin
has a new13.0.0
release: https://www.npmjs.com/package/firebase-adminfirebase-functions
(latest release:6.1.0
), you get an npm error: https://www.npmjs.com/package/firebase-functions?activeTab=readmefirebase-functions
has an explicit peer dependency on previous version offirebase-admin
:Steps to reproduce:
firebase-admin
andfirebase-functions
npm install
The text was updated successfully, but these errors were encountered: