Typescript types missing when upgrading from 10.2 to 10.3

[shaunpersad]

Operating System

All

Browser Version

All

Firebase SDK Version

10.3

Firebase SDK Product:

Auth

Describe your project's tooling

React app with Vite inside a monorepo

Describe the problem

I recently had to upgrade our firebase SDK from 9 to 10 and discovered the Typescript types have completely gone missing. I was able to test out exact versions of the 10.x SDK and saw that types were correctly found up until version 10.3.0. Auth is the only part of the SDK we use so I did not test out the other products to see if they also have the same issue.

Steps and code to reproduce issue

npm install --save-exact firebase@10.2 => autocomplete from types are available
npm install --save-exact firebase@10.3 => autocomplete from types are not available

[hsubox76]

That's really odd, the only change in Auth I see between 10.2 and 10.3 is a change for React Native users: #7570

Are you using React Native? If so, check out this comment (and the surrounding issue) and see if it's related to what you're experiencing: #7584 (comment) In this issue, it only affects the VSCode editor autocomplete. It doesn't affect the actual build. Is that what you're seeing?

If you're not using React Native: Can you provide a minimal repro? I'd like to find out which path your project follows to try to find the typings. Ideally I would like to see the full structure and build tooling of your project (vite config, monorepo setup, etc), but I don't need to see any of your code except maybe a single line where you try to import types.

[google-oss-bot]

Hey @shaunpersad. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@shaunpersad if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.