v4.2.3 is not published on npm

FirebaseExtended / reactfire

Hooks, Context Providers, and Components that make it easy to interact with Firebase.

https://firebaseopensource.com/projects/firebaseextended/reactfire/

MIT License

3.54k stars 401 forks source link

v4.2.3 is not published on npm #570

Open oudmane opened 1 year ago

oudmane commented 1 year ago

I encountered a weird bug with useUser, status is success in the start, I went down a rabbit hole just to realize that v4.2.3 fixes the bug but it is not published on npm.

1nterfect0r commented 1 year ago

Easy to fix. Please do it

Gbuomprisco commented 1 year ago

The library is virtually unmaintained. It's a shame.

webbertakken commented 1 year ago

The API of the repo is much better than any other firebase lib I've seen over the years. Definitely a shame to see it go unmaintained.

Seems the latest refactor was very complex but is as good as finished. It is listed as the de facto bindings for React, which very much isn't dead or going to be anytime soon. A bit of renewed energy could really make this repo shine again. Which begs the questions:

Is there anything we can do to support you maintainers?
Is there any chance we could get some Googlers to support this project?

I guess you'd be the best person to ask @jhuleatt.

jhuleatt commented 1 year ago

Whoops, thanks all, I've published 4.2.3. We're hoping to give the ReactFire repo a cleanup this week, and are also working on a longer-term plan both for maintenance and for if/how we integrate with the new React stuff like server components.

If anyone has a specific issue that's bugging them, please respond here and I'll prioritize it during this week's cleanup!

devth commented 1 year ago

Thanks @jhuleatt, very excited to see activity on this project!

A couple pain points I run into regularly:

https://github.com/FirebaseExtended/reactfire/issues/577 - update types to reflect the fact that data will initially be undefined
https://github.com/FirebaseExtended/reactfire/issues/463#issuecomment-1557302485 - I know you previously stated your opinion on this issue, but maybe worth revisiting? I think it actually pairs really nicely with #577 above.

webbertakken commented 1 year ago

Thank you @jhuleatt! Very exciting indeed!

If I may say so:

The docs are in a bit of an in-between state between old and new approaches, and the examples aren't available on the website for the docs. Perhaps we could set up an improved docs website based on something like Docusaurus, which natively supports markdown based docs and tailors to fairly straight forward setup for docs and blogs. Another upside of it would be that people can easily suggest changes to the docs, thanks to the "Edit this page" link a the bottom of docs pages (I'd be happy to draft a PR for this if it helps)
I believe a complete example showing authentication in combination with auth/user restricted pages (or components) that work seamlessly without a page reload would help onboard many people. Ideally based on the newest approach and with the fix for useAuth / useUser in.