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
Other (e.g. Ionic/Cordova, Node, browser, operating system):
How to reproduce these conditions
ng add with a new version of Angular which doesn't have a corresponding version of @angular/fire with matching peer dependencies succeeds with v0.0.0 of @angular/fire:
$ ng new foo-app
$ cd foo-app
$ ng add @angular/fire
ℹ Using package manager: npm
✔ Found compatible package version: @angular/[email protected].
✔ Package information loaded.
The package @angular/[email protected] will be installed and executed.
Would you like to proceed? Yes
✔ Packages successfully installed.
Package "@angular/fire" was found but does not support schematics.
Expected behavior
ng add should fail
Actual behavior
ng add does not fail due to @angular/[email protected] satisfying the peer dependencies of the CLI.
The text was updated successfully, but these errors were encountered:
Note this issue reappears each time a newer version of Angular is released. The issue persists until a compatible version of AngularFire is made available. During the period of brokenness, users are unable to ng add @angular/fire per the documentation (https://angular.dev/tools/cli/deployment).
Version info
Angular:
N/A
Firebase:
N/A
AngularFire:
N/A
Other (e.g. Ionic/Cordova, Node, browser, operating system):
How to reproduce these conditions
ng add
with a new version of Angular which doesn't have a corresponding version of@angular/fire
with matching peer dependencies succeeds with v0.0.0 of@angular/fire
:Expected behavior
ng add
should failActual behavior
ng add
does not fail due to@angular/[email protected]
satisfying the peer dependencies of the CLI.The text was updated successfully, but these errors were encountered: