Skip to content

Deprecate @angular/[email protected] #3480

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

Closed
mgechev opened this issue Dec 20, 2023 · 3 comments
Closed

Deprecate @angular/[email protected] #3480

mgechev opened this issue Dec 20, 2023 · 3 comments

Comments

@mgechev
Copy link
Member

mgechev commented Dec 20, 2023

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:

$ 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.

@google-oss-bot
Copy link

This issue does not seem to follow the issue template. Make sure you provide all the required information.

@fredsa
Copy link

fredsa commented Dec 20, 2023

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).

A quick search through the issues reveals users have been regularly affected: #3321, #3467, #3290, #3235, #3162, #3105, #3044, #2832, #2830.

@jamesdaniels
Copy link
Member

v0.0.0 has been deprecated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants