GoogleAuthProvider not exported anymore in v18

[jnizet]

GoogleAuthProvider not exported anymore in v18

[jamesdaniels]

@angular/[email protected] has the fix, cutting 18.0.1 now

[anisabboud]

Same issue with Timestamp, ReCaptchaV3Provider, and Email/Facebook/Google/Phone AuthProviders.
Works with AngularFire 17.1.0, but not with 18.0.0.

$ ng serve
Application bundle generation failed.


✘ [ERROR] No matching export in "node_modules/@angular/fire/fesm2022/angular-fire-firestore.mjs" for import "Timestamp"

        │ import { Timestamp } from '@angular/fire/firestore';


✘ [ERROR] No matching export in "node_modules/@angular/fire/fesm2022/angular-fire-app-check.mjs" for import "ReCaptchaV3Provider"

        │ import { ReCaptchaV3Provider, initializeAppCheck, provideAppCheck } from '@angular/fire/app-check';


✘ [ERROR] No matching export in "node_modules/@angular/fire/fesm2022/angular-fire-auth.mjs" for import "EmailAuthProvider"
✘ [ERROR] No matching export in "node_modules/@angular/fire/fesm2022/angular-fire-auth.mjs" for import "FacebookAuthProvider"
✘ [ERROR] No matching export in "node_modules/@angular/fire/fesm2022/angular-fire-auth.mjs" for import "GoogleAuthProvider"
✘ [ERROR] No matching export in "node_modules/@angular/fire/fesm2022/angular-fire-auth.mjs" for import "PhoneAuthProvider"

        │ import { EmailAuthProvider, FacebookAuthProvider, GoogleAuthProvider, PhoneAuthProvider } from '@angular/fire/auth';

[jamesdaniels]

It appears to be a bug with the RC version of ng-packagr mangling fesm2022 so export * was not workign correctly, which I embarrassedly cut final against. This appears to be resolved in the final release, pushed a commit to main branch now which I was testing against, hopefully the canary will prove the fix and I can cut 18.0.1

[jonathansigg]

I have still a problem with appcheck on web

provideAppCheck(() => {
    const provider = new ReCaptchaV3Provider(recaptcha3SiteKey);
    return initializeAppCheck(undefined, { provider, isTokenAutoRefreshEnabled: true });
  }),

This gets me everytime the "document is not defined error", and i can't find any fix, that is working.

[google-oss-bot]

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

[SebApptien]

Same for Geopoint :

X [ERROR] No matching export in "node_modules/@angular/fire/fesm2022/angular-fire-firestore.mjs" for import "GeoPoint"

[docaohuynh]

I have got same error when upgrade to angular 18, AngularFire 18.0.0
Error: export 'GoogleAuthProvider' (imported as 'GoogleAuthProvider') was not found in '@angular/fire/auth' (possible exports: Auth, AuthInstances, AuthModule, applyActionCode, authInstance$, authState, beforeAuthStateChanged, checkActionCode, confirmPasswordReset, connectAuthEmulator, createUserWithEmailAndPassword, deleteUser, fetchSignInMethodsForEmail, getAdditionalUserInfo, getAuth, getIdToken, getIdTokenResult, getMultiFactorResolver, getRedirectResult, idToken, initializeAuth, initializeRecaptchaConfig, isSignInWithEmailLink, linkWithCredential, linkWithPhoneNumber, linkWithPopup, linkWithRedirect, multiFactor, onAuthStateChanged, onIdTokenChanged, parseActionCodeURL, provideAuth, reauthenticateWithCredential, reauthenticateWithPhoneNumber, reauthenticateWithPopup, reauthenticateWithRedirect, reload, revokeAccessToken, sendEmailVerification, sendPasswordResetEmail, sendSignInLinkToEmail, setPersistence, signInAnonymously, signInWithCredential, signInWithCustomToken, signInWithEmailAndPassword, signInWithEmailLink, signInWithPhoneNumber, signInWithPopup, signInWithRedirect, signOut, unlink, updateCurrentUser, updateEmail, updatePassword, updatePhoneNumber, updateProfile, useDeviceLanguage, user, validatePassword, verifyBeforeUpdateEmail, verifyPasswordResetCode)

[jamesdaniels]

Hmmm that odd, I'll explore what might have happened with these exports. Presumably Typescript 5.4 is fighting our build pipeline

[jnizet]

Thank you so much for the quick fix and the quick release.

[jamesdaniels]

@jnizet NP, thank you for reporting!

We'll get our current test suite gap closed, so we're actually using the canary bundle in an integration test with a sample app, so we can catch build problems like this before they hit prod.