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-rules-testing

v0.6.2

Published

Dependency-free offline testing for firebase rules with descriptive feedback.

Downloads

6

Readme

Firebase Rules Testing

Easy testing of compiled firebase rules with descriptive feedback on failures.

Instalation

npm install firebase-rules-testing

Motivation

Firebase is a great Tool for easily getting your project up and running. But when you grow security gets more important. Firebase rules are flexible and allow a great extent of custom control. But they get quite fast very complex and difficult to understand. The Bolt Language and Compiler goes a long way to simplify this complexity and make it manageable.

That's fine until somthing you think should work doesn't. Do debug we still have to check the compiled rules:

Their manual states:

We welcome experimentation, but ask that you hand-verify the resulting JSON output before using with production applications. https://github.com/firebase/bolt#-bolt-compiler

So we're back to that complexity. We can use the firebase simulator for simple read and set requests. In real life multilocation updates are often used and enforced by rules. These can't be tested easily.

This package aims to take all your requests as they are and test them automatically against every rule set you generate. Also you can test requests you don't want to work. In case of failure to meet your assumptions you get detailed feedback which rule (.read, .write or .validate), on which path suceeded and failed with which environment (like path variables). Don't spend time seraching for your mistakes use it for fixing them.

What it is:

  • Detailed information for where a request fails.
  • Use it for Bolt compiled (syntactically valid) rules.
  • Tester for logical mistakes.

What it is not:

  • Syntax checker (typos in rules, illeagal/unsupported functionality in rules)
  • Request checker (invalid requests => undefined behavior)

Project status

We use it in production for a small start-up app. It woks for us, but can be certainly improved - collaboration is more then welcome!

What's there?

  • The environment is complete (root, data, newData, now, auth). That is except for details on the auth-object (everything except auth.uid).
  • Server timestamp is supported in request as {'.sv': 'timestamp'}
  • Set data from JSON export of your database.
  • Get detailed information if test fails: currently as JSON object.
  • Every suported feature is used/tested in test.js. This is currently the only documentation as well. I hope the api is quite small and self explanatory.

What's missing?

  • API-documentation
  • Nice readable feedback of failed test information (instead of JSON printout)
  • coplete auth-object implementation
  • althoug it's quite fast (thanks modern JS engines), there are a lots of oportunities for performance improvements.
  • your idea?