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

@worldbrain/storex-backend-firestore

v0.1.1

Published

Firestore backend for Storex

Downloads

16

Readme

Firestore backend for Storex.

Usage

$ npm install @worldbrain/storex @worldbrain/storex-backend-firestore

See main Storex repo for futher docs

Limitations

  • You can only sort by one field, and that field must be the one you're filtering by (Firestore docs)
  • You cannot use the $ne operator (Firestore docs)
  • No logical ORs (Firestore docs)
  • Skipping the first X items in an ordered retrieve is done client-side, so it is recommended to increase the lower limit of your resultset instead (findObjects({foo: {$gt: X + Y}}) rather than findObjects({foo: {$gt: X}, {skip: Y}}))

TBD

  • Automatic security rule generation
  • Ability to easily move StorageModules to Firebase Functions
  • Back-end agnostic automatic processes, which whould be Firebase Functions listening to certain queries in this backend
  • Subcollection support (after investigations on real-world performance benefits)
  • Media field support integrating with Firebase Cloud Storage

Note: Firebase Realtime database support should be a separate back-end

Development

Create a new Firebase project for unit testing, and create the file <this-repo>/private/firebase.json (in .gitgnore so it doesn't accidentally go public) with the following contents:

{
    "apiKey": "xxxx",
    "authDomain": "xxx.firebaseapp.com",
    "databaseURL": "https://xxxx.firebaseio.com",
    "projectId": "xxxxx",
    "storageBucket": "xxxx.appspot.com",
    "messagingSenderId": "xxxxx"
}

Then continuously run the tests while developing:

$ npm run test:watch