npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

firebase-dbfake

v1.0.0

Published

A fake object library to aid in unit testing code that has Firebase as a data store.

Downloads

36

Readme

firebase-dbfake is a fake library to assist you in unit testing your JavaScript projects that store data in Firebase.

Quick Overview

When you store data in firebase, you have two basic objects that you interact with:

  • reference describes the location in your document store you would like to work with
  • dataSnapshot a representation of the data at a reference

Don't Mock What You Do Not Own

The book Growing Object Oriented Software, Guided by Tests states that you should never mock interfaces that you don't own. firebase-dbfakes is designed to make it simple for you to obey this principle. When you call once() on a reference, you get back a promise and if all goes well that resolves to a DataSnapshot. The core principle that started firebase-dbfake is that you don't own once() and you should have a shim that calls it. The shim returns you a promise which resolves to a DataSnapshot. Once you have that in place, you can inject a firebase-dbfake.snapshot and unit test to your hearts content.

firebase-dbfake

firebase-dbfake exposes four methods to help you in your unit testing:

  • reference returns you an object with the same api as a real Firebase reference, but it doesn't do much of anything. It does enable you to supply your own behavior needed for your tests.
  • snapshot returns you an object with the same api as a real Firebase dataSnapshot, but it won't connect to Firebase.
  • resolveSnapshot returns a promise that resolves a snapshot. You should use this when you mock your code that would interact with Firebase.
  • memoizeSnapshot a short hand for writing a function that returns a promise which resolves a snapshot. Again, used when mocking your data layer.