This made me sad to hear. Rest in peace. 🕊️

I don't have the bandwidth to contribute much right now. Best of luck!

Please let us know if/when you complete the name dispute on NPM; there are some important issues that need to be addressed in the library. (on whichever fork becomes connected to the npm module)

Also: Rest in peace, Brian! 🕊

I've now gone back and forth with NPM and they are sticking to their standard four-week deadline for package owners to respond to name disputes. So the soonest we could expect to get publish permissions is 1 December.

For now I'll begin publishing updates from my fork. Anyone who wants an issue or PR prioritized is welcome to re-open it there. We'll start with a 2.3.0 release incorporating whichever open PRs are ready, and then work toward a 3.0.0 release to get up to date with the previous year's breaking changes to the Firebase SDK.

Rest in peace. 💐

Hi again. We're working on clearing up the pull request backlog. Track our progress here. I could use some assistance getting the following pull requests ready to merge:

onSnapshot support (needs a few more tests; check with @zeevl to make sure you're not duplicating effort as he's been working on this recently.)
Add user.toJSON (needs tests)
Update jest.md (needs to be clarified)

Let me know if you have a few minutes to help out.

NPM's four week response period ended on Friday so I am expecting action from them this week. I followed up with their support team to move things along.

The three pull requests above are important changes that are almost ready to merge. Please help us out and try to finish one if you can.

NPM now telling me they won't act before 10 December.

firebase-mock@2.3.0 has been published to NPM. Happy hacking!

Please point NPM to your repo where the code for 2.3.0 and 2.3.1 is. It still points to this repo which hasn't had commits since 2018.

Thanks, v2.3.2 has been published with the correct repo URL. No other changes from 2.3.1.