add angular v17 support

[DimitriTsikaridze]

Version info

Angular:

Firebase:

AngularFire:

Other (e.g. Ionic/Cordova, Node, browser, operating system):

How to reproduce these conditions

Failing test unit, Stackblitz demonstrating the problem

Steps to set up and reproduce

Sample data and security rules

Debug output

** Errors in the JavaScript console **

** Output from firebase.database().enableLogging(true); **

** Screenshots **

Expected behavior

Actual behavior

[woutersteven]

I think if you upgrade from v16 to v17 using the schematics, AngularFire v16 will continue to work, but other NPM updates will break due to dependency issues. I think they will release v17 pretty soon, since they matched versioning to match Angular and looking at the tags, there's already a pre-release version tagged: 17.0.0-next.0

[DimitriTsikaridze]

maybe but I'm currently having issues where when I run ng add in v17 angular/fire it doesn't find compatible package

[Hambat]

any news?

[nolansingroy]

I am having same issues. I created a angular project in 17 but adding angular fire does not support schematics

ng add @angular/fire
Skipping installation: Package already installed
Package "@angular/fire" was found but does not support schematics.

[sergiotome]

+1 here. Need Angular Fire updated to be compatible with Angular 17.

[rpaivabr]

+1

[gazz9ar]

Is there a way to ignore the conflicting dependency until we get the release 17?

[DimitriTsikaridze]

Is there a way to ignore the conflicting dependency until we get the release 17?

maybe with legacy peer deps or force or both, I haven't tried yet

[gazz9ar]

Is there a way to ignore the conflicting dependency until we get the release 17?

maybe with legacy peer deps or force or both, I haven't tried yet

I run npm i --legacy-peer-deps and the login I had with firebase still works

[woutersteven]

You can configure an "overrides" block inside package.json to override which package versions are used for a given package, however I personally think this is a last resort and only use it for packages that i have tot keep, but are unmaintained. In most cases, I will wait for an update.

You can also look at the NPM package "npm-force-resolutions", but again, as a last resort.

[PierreDuc]

For me it worked to just do ng add @angular/fire@next. But this was with a new project

[woutersteven]

For me it worked to just do ng add @angular/fire@next. But this was with a new project

Great idea, I've immediately tried that in existing projects. Not sure why I didn't consider that.

I had to make some manual changes to dependencies, but it seems to be working (for me) with: (listing relevant packages only):

• Angular v17.0.2
• AngularFire v17.0.0 (next)
• Angular PWA v17.0.0
• Firebase v10.6.0

I'm using the following features and they work as expected. Storage, Firestore, Hosting, Authentication, Messaging, Cloud Functions (v1 and v2) and AppCheck (monitoring only at the moment).

Notes:

1. Running the schematics will recreate configuration files for Firebase. It will possibly update main.ts, angular.json and firebase.json, on top of package.json. So if you're not sure, make sure to make backups of those first. If you are using a repo, you can view changes afterwards and revert/update as needed.
2. Installing @next versions in production environments should be done with care. They're usually pre-release versions and may still need further testing or more development.

When AngularFire v17 comes out, its trivial to replace the next version with the main one.

[lorenzbaum]

A working v17 would be fantastic, as with @next the deployment does not work (jet):

With ng build and the new builder (@angular-devkit/build-angular:application) now creating subfolders for browser and eventually server, Firebase uploads it including those folders, rendering the Angular web app corrupted.

Edit: Here is the PR for firebase-tools... this still needs to be published. firebase/firebase-tools#6480

[sergiotome]

any update on this? @jamesdaniels , can we at least get a tentative date on when a final version for v17 could be ready?