Firebase v0.2

[alexluong]

No description provided.

[Marcusg62]

@alexluong Hi, do you need help maintaining this project? Would love to get this plugin back on track for the community. :)

[alexluong]

Thanks @Marcusg62 for the offer! I apologize for abandoning the plugin lately. I'd appreciate any help I can get.

I haven't used the plugin for a while, so I'm not sure how compatible the plugin is with the latest versions of Gatsby (#19 #23 #31 #32). If you can provide some sort of summary on how it's doing and confirm those issues, that would be a great start!

I think the plugin API is stable enough to release the v1.0 version, once all the issues are sorted out.

[Marcusg62]

@alexluong Sure, no problem! I've been looking for a project to work on and I can see myself using this one a lot.

From what I gather in my own experience and viewing open issues, everyone is loving the plugin until they run gatsby build. I think this is because we are not using the useFirebase hook/context described here.
However, that documentation does not show up on the plugin page on gatsbyjs.com,
If we can confirm that issues like #31 are caused by this then we could simply update the readme and I think we would be back on track.

[alexluong]

@Marcusg62 You should disregard the doc page on GitHub (https://github.com/alexluong/gatsby-packages/tree/master/packages/gatsby-plugin-firebase). It's v0.1 documentation.

I basically work on the v2 branch and publish the plugin from there, so the doc on Gatsby site or npm are more accurate.

In v2, useFirebase is not part of the plugin's API anymore.

[Marcusg62]

@alexluong Oof, okay it seems we have some real investigation to do then. Let me get a public repo to you so the issue can be recreated. Sound good?

[alexluong]

Yup that would be fantastic. Thank you!

[Marcusg62]

I have added a comment to an existing issue since it seems to be the same problem. I added a link to the repository there. :) #31 #