-
Notifications
You must be signed in to change notification settings - Fork 892
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typescript 5.4.5 tsc
failing against firebase 10.11.1
#8222
Typescript 5.4.5 tsc
failing against firebase 10.11.1
#8222
Comments
Thank you so much for the great minimal reproduction project with steps! I was able to successfully reproduce the issue, and we are looking into it. |
Made some progress, a couple of things to note:
So I think the problem is that the typings for webchannel and cordova aren't run through the dts rollup the way that auth-public.d.ts is (using api-extractor), which rolls up all the scattered d.ts files into one. Instead it points to an entry point d.ts which points to a cascade of other files. Seems that yarn4 (or TS 5, or some combination) isn't able to navigate all those files the way we expect. The correct solution is probably to run dts rollup steps, probably using api-extractor, or maybe rollup can do it, on the webchananel and cordova typings files to bundle them into one. We should NOT reuse auth-public.d.ts for those entry points since they're both missing some symbols or have some extra ones compared to the regular auth entry point. |
Operating System
macOS 14.4.1
Browser Version
N/A
Firebase SDK Version
10.11.1
Firebase SDK Product:
Auth, Database
Describe your project's tooling
typescript@5.4.5 and yarn@4.2.1 (both with PnP and node-modules as linkers). We use firebase within a Chrome extension we ship.
Describe the problem
After upgrading to Firebase 10.11.1, and adding an import to the new
firebase/auth/web-extension
, we're seeing TypeScript'stsc
failing.Steps and code to reproduce issue
yarn
yarn tsc
More context
Locally, we can sort of hedge around this with some module augmentations, but it'd be nice to not have to do this.
The text was updated successfully, but these errors were encountered: