Consider adding modular Firebase SDK 9 support

[jquesada2016]

This will be a breaking change going forward with this library. It is possible to still make this library work, however, a custom object that has all of the expected methods must be passed in. For now, Firebase SDK 9 has a compat surface, so users can use that in the meantime, but doesn't reap the benefits of the tree-shaking.

[LockedThread]

I second this

[Kimeiga]

I third this. I wish I knew enough about this to write a proper issue, but I'm going back to my Sveltefire projects, npm installing (which upgrades them to lockfile version 2), and redeploying them to Firebase Hosting and getting LOADS of errors. Either the Google sign in button doesn't do anything (merely just auth.signInWithPopup(googleProvider)) or the routes don't load or something. No errors in console. I think it might have something to do with the new firebase api?

[madeleineostoja]

imo a breaking change for Firebase 9 isn’t an issue. Users that need to stick with Firebase 8 for whatever reason can stay on an old version of sveltefire, this is exactly the reason semver exists.

Firebase 9 support should be implemented fully, rather than trying to monkeypatch compat with Firebase 8

[codediodeio]

Firebase 9 support added in #74

[Kimeiga]

Hey Jeff, would there be any chance you could add more documentation to the Readme for how to add new documents to collections and other adding stuff using the new structure of sveltefire?