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

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

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

Angular 17.1 is coming out soon (currently at next.2 version which adds support for TypeScript 5.3. Perhaps AngularFire will add support for TypeScript 5.3 as well and that's what they're...

I saw that @angular/fire v17 has been released, I've tried it (replaced the pre-release version) and everything seems to be working on my end. I'll do a few more tests...

Thank you for the reply, I tried it around for a while. The problem / conflicting issue is parentElement: "body", Without it , it works, with it, it appears behind...

Also experiencing this during serve

It may be useful for others, for me it is working for me on Angular `17.3.8` and `npm` with the following in `package.json`: ```TypeScript "dependencies": { "@supabase/supabase-js": "2.43.1", }, "devDependencies":...

Curious about the progress :)

Thank you for the fast reply, that worked!