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 🙏

© 2024 – Pkg Stats / Ryan Hefner

firebase-copy

v0.2.0

Published

Create a copy of the Firebase constructor with its own global state

Downloads

191

Readme

firebase-copy Build Status

Create a copy of the Firebase constructor with its own global state

Install

$ npm install --save firebase firebase-copy

Usage

var firebaseCopy = require('firebase-copy');

var Firebase = require('firebase');
var Firebase1 = firebaseCopy();
var Firebase2 = firebaseCopy();

// Firebase1 and Firebase2 will behave just like Firebase, but without the shared state.

var ref1a = new Firebase1('https://my-firebase.firebaseio.com/some-path');
var ref1b = new Firebase1('https://my-firebase.firebaseio.com/some-path');
var ref2 = new Firebase2('https://my-firebase.firebaseio.com/some-path');

ref1a.on('value', () => console.log('1a'));
ref1b.on('value', () => console.log('1b'));
ref2.on('value', () => console.log('2'));

ref1a.set('some-value');
console.log('end');

// output is:
// 1a
// 1b
// end
// 2

In the above example ref1a and ref1b share some global state with each other, so listeners fire synchronously without round-tripping to the server. ref2 must wait for data to round-trip to the server before seeing it's listener fire.

Essentially, ref2 behaves like it is on a completely different machine from ref1a and ref1b.

This is useful for testing interactions of multiple clients from a single machine.

License

MIT © James Talmage