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-noserver

v3.0.0-alpha10

Published

firebase-noserver ===================

Downloads

2

Readme

firebase-noserver

A serverless request / response architecture based on firebase and firebase queues. Firebase is an excellent platform for building most data driven applications, and for the most part you do not need to expose a backend and have to worry about the security of your app. However, there are some actions that require a request-response type of architecture. While you can have event listeners for when data changes, that approach can gets rather complicated, and it doesn't take into account those changes that should only happen in secured data where a user doesn't have access, or actions that have no side effects in the data at all. Firebase-noserver does the dirty work for you to handle notification of when an action completes, getting a response in plain JSON, and error handling when an action fails.

Requirements

Installation

npm install --save firebase-noserver

Quick Start

For use with version 3.x of the firebase node library, use the 3.x branch, or for version 2.x, use the 2.x branch.

For the queue side:

const firebase = require('firebase');
const createQueue = require('firebase-noserver');

firebase.initializeApp({...});

// all methods in jobMap must return promises
const jobMap = {
  echo: (client, val) => Promise.resolve(val),
  ping: (client) => Promise.resolve(Date.now()),
  fail: (client) => Promise.reject('Always fails'),
  somethingComplicated: (client, payload, firebase) => {
    const auth = client.auth;
    const userId = auth && auth.uid;
    
    const result = ... // do your magic here

    return Promise.resolve(result);
  }
};

const options = {}; // nothing here, yet

const queue = createQueue(firebase, 'clients', 'queues/clients', jobMap, options);

And for the client side:

const firebase = require('firebase');
const createClient = require('firebase-noserver/client');

firebase.initializeApp({...});

const options = { timeout: 1000 };

const createRequest = createClient(firebase, 'clients', 'queues/clients', options);

createRequest('echo', 'blah').then(val => { // should be 'blah'
  return createRequest('ping');
}).then(timestamp => { // should be the timestamp on the queue
  return createRequest('fail');
}).then(val => { // this shouldn't be reached
}).catch(err => { // should be 'Always fails'
  console.error(err);
};