Broken link to FirebaseError

[marcusx2]

The AuthError says that it extends FirebaseError but the hyperlink leads to a 404 not found...

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[hsubox76]

Thinking out loud for JS SDK team: This is going to be a little tricky. The FirebaseError class comes from the util package which is an internal package and therefore not in the public documentation. We do re-export it from @firebase/app but this isn't enough as Auth and other libraries import the class from util directly. We could have them import from app instead but I suspect api-documenter will still follow the reference back to util.

We can also create a FirebaseError interface from scratch in @firebase/app and export that instead of reexporting the actual FirebaseError class from util. This could break users who are already importing and using FirebaseError as a class somehow though (maybe to do instanceof checks). Also JS SDK contributors in every package would have to be careful about every single usage, whether you want to import the class from util or the interface from app, which seems like a recipe for human error.

The other option is to add @firebase/util to the reference docs, which could cause more confusion in the reference docs.

[evilDave]

There is a problem currently with the way FirebaseError is being used, instanceof checks fail due to this. (It is not working with 10.10.0, was working with version 9.23.0, maybe later)

[hsubox76]

Which specific instanceof FirebaseError checks are failing? Some auth errors? All auth errors? Other products or just auth? Can you make a separate issue for this with examples?