The convience observables provided by the Auth module are no longer type safe

docs/auth.md に記載されている利便性用 observable から始め、Auth モジュールで使用されている rxfire/auth の import を追跡します。Angular CLI 18 の tsconfig.json における moduleResolution "bundler" での解決を v17.1.0 およびリンク先の Angular CLI commit と比較します。完了の条件は、現在のセットアップで observable が期待される型を維持することです。

Version info

Angular CLI: 18.0.2
Node: 22.2.0
Package Manager: npm 10.8.0
OS: linux x64

Angular: 18.0.1
... animations, common, compiler, compiler-cli, core, fire
... forms, platform-browser, platform-browser-dynamic, router

Package Version

@angular-devkit/architect 0.1800.2
@angular-devkit/build-angular 18.0.2
@angular-devkit/core 18.0.2
@angular-devkit/schematics 18.0.2
@angular/cli 18.0.2
@schematics/angular 18.0.2
rxjs 7.8.1
typescript 5.4.5
zone.js 0.14.6

How to reproduce these conditions

Failing test unit, Stackblitz demonstrating the problem
n/a

Steps to set up and reproduce

• Create a new angular app using the latest version of the cli
  ng new angular18-firebase-test
• Add AngularFire
  ng add @angular/fire
• Follow the guidance here to add the convenience observables

Sample data and security rules
n/a

Debug output

** Output from firebase.database().enableLogging(true); **
n/a

** Screenshots **

Expected behavior

The convenience observables should be properly typed as they were in v17.1.0
Note in this screenshot how the IDE properly recognizes the types when using the previous release:

Actual behavior

The observables are cast as any (see screenshot).

Edit 1
Upon further investigation, it appears the problem is related to how the rxfire/auth module in this file is imported. Following the import through to the definition of the module takes me to a type definition file in v17 but instead goes to an esm module in v18. See related screenshot here:

Still unsure why this is happening.

Edit 2
Eureka! It appears in this commit the AngularCLI now defaults to setting the moduleResolution compiler option in the tsconfig.json file to "bundler" by default thus causing the module to get resolved differently. Switching back to the value of "node" allows for the proper import of typed entities but likely causes problems with the areas targeted in that aforementioned commit.