stripe-firebase-extensions VS react-firebase-hooks

Stripe was the most difficult and finicky aspect of the migration. Within firebase, I used the stripe firebase extension to manage all the stripe components. It took care of a lot of the implementation work so I had no idea how to approach this when I first started. I bounced between different ideas like bi-directional sync of the subscription tier within firebase, but eventually I settled upon using Stripe as my single source of truth. Although it’d be more involved, I knew it’d make fully cutting Firebase out of Fleeting Notes easier down the road. Here are the migration steps I settled upon:

In this example, we are going to use the Stripe Payment Extension updates, which will allow an enhancement of the Stripe Webhook events. In this example, we are going to focus on when a product has been created.

A little bit fatter in terms of size and not actively maintained.

React-firebase-hooks

I'm trying to figure out how to use react-firebase-hooks in my react app so that I can simplify calls on my database.

You also might benefit from leveraging react-firebase-hooks. I’ve been really liking using it. https://github.com/csfrequency/react-firebase-hooks

For a good while, I've been relying on a little package called react-firebase-hooks to turn my Firebase realtime document fetching into tidy hooks. However, this library has become a bit sketchy since the release of Firebase v9 a.k.a the Modular edition.

For example, this issue, this issue, is already handled out of the box - and a lot of the other ones are already solved since React Query does all of the hard work.

If you want, you can use useFirebaseAuth which takes care of onAuthStateChanged for you in a clean and simple way. That library also has useful hooks for working with Firestore and RTB.

I believe this should be fixed soon, as chrisbianca says on Github https://github.com/CSFrequency/react-firebase-hooks/issues/104#issuecomment-778586537