You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a project that uses both firebase-admin and firebase-js-sdk (e.g. using workspaces), the version of shared components like @firebase/database can misalign causing each package to use different versions. This also means type definitions that are used by user code will conflict depending on which type definitions are highest up in node_modules.
firebase-admin relies on @firebase/database@0.5.x whereas firebase-js-sdk relies on 0.6.x.
I would strongly recommend as a fix to bump all @firebase/package modules to 1.x to properly reflect semver and avoid this. 0.x is meant for initial development versions and firebase-js-sdk is meant to be production-ready.
[REQUIRED] Describe your environment
[REQUIRED] Describe the problem
In a project that uses both firebase-admin and firebase-js-sdk (e.g. using workspaces), the version of shared components like @firebase/database can misalign causing each package to use different versions. This also means type definitions that are used by user code will conflict depending on which type definitions are highest up in
node_modules
.firebase-admin relies on @firebase/database@0.5.x whereas firebase-js-sdk relies on 0.6.x.
I would strongly recommend as a fix to bump all @firebase/package modules to 1.x to properly reflect semver and avoid this. 0.x is meant for initial development versions and firebase-js-sdk is meant to be production-ready.
https://semver.org/#spec-item-4
As firebase-admin uses caret ranges, minor changes at 1.x won't trigger duplication while 0.x will.
https://docs.npmjs.com/misc/semver#caret-ranges-123-025-004
Steps to reproduce:
Relevant Code:
No code involved.
The text was updated successfully, but these errors were encountered: