Error: node_modules/@firebase/auth/dist/auth-public.d.ts:3225:23 - error TS2304: Cannot find name 'FactorId_2'.

[jnizet]

[REQUIRED] Describe your environment

• Operating System version: macOS 13.1
• Browser version: NA
• Firebase SDK version: 9.19.0
• Firebase Product: auth

[REQUIRED] Describe the problem

Steps to reproduce:

• Try to compile an Angular project using Firebase 9.19.0
• The compilation fails with the error

Error: node_modules/@firebase/auth/dist/auth-public.d.ts:3225:23 - error TS2304: Cannot find name 'FactorId_2'.

The auth-public.d.ts file does indeed seem to reference a FactorId_2 symbol that doesn't exist.

It's documented as excluded at line 1160 of the file:

/* Excluded from this release type: FactorId_2 */

[eun-choi]

+1

[ng] Build at: 2023-03-31T00:13:15.682Z - Hash: cd01b281d54b92c9 - Time: 107314ms [ng] [ng] Error: node_modules/@firebase/auth/dist/auth-public.d.ts:3225:23 - error TS2304: Cannot find name 'FactorId_2'. [ng] [ng] 3225 static FACTOR_ID: FactorId_2; [ng] ~~~~~~~~~~ [ng] [ng] [ng] [ng] ✖ Failed to compile.

[dwyfrequency]

@jnizet or @eun-choi, can you provide a minimal reproducible repo?

[duncanchiu409]

I am using firebase version: ^9.6.7 . Had the same issue

[duncanchiu409]

This is my reproduced error repo. Hope helps. Pretty simple to reproduce the problem.
https://github.com/duncanchiu409/firebase-issue7174

[jnizet]

Here's mine (this PR specifically, which upgrades to the latest version: jnizet/maison-solidaire#147).

Steps to reproduce:

• clone the repo and checkout that branch
• yarn
• yarn build

[PrajinThunoli]

Same for me too
node_modules/@firebase/auth/dist/auth-public.d.ts:3225:23 - error TS2304: Cannot find name 'FactorId_2'.

3225 static FACTOR_ID: FactorId_2;

Did a npm update and build this issue came up

[hassan-badat]

A temporary work around is to add the value:

"skipLibCheck": true

to your tsconfig.json

[jbalidiong]

Thanks for sharing the minimal repro @jnizet and @eun-choi. I was able to replicate the error with the latest version of our SDK. Let me check what we can do for this issue or bring someone from the Auth team that can provide more context about it. I’ll update this thread if I have any information to share.