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

grid-cms

v1.5.1

Published

The easiest way to manage data in Firestore.

Downloads

138

Readme

GRID/CMS

The easiest way to manage data in Firestore.

Integrates with Firebase Hosting to provide a simple self-updating CMS with zero maintenance.

Getting started

  1. Go to firebase project (or firebase init in a blank folder) and make sure hosting and Firestore is setup.

  2. Then run npm init cms and follow instructions.

  3. Login and define what data you want exposed in the CMS.

Hosting and config

GRID/CMS will automatically read the firebaseConfig from the hosting environment, unless specifically defined. This makes it easy to have prod, dev and testing environments without a bunch of .env files.

Permissions

The schema will be saved in Firestore (/_CMS_/schema) and the current user will therefore need read/write access.

  • If write access is given the user will be able to extend the schema.

  • If only read access is given, the user will be able to login and manage data but not extend the schema.

An example of admin access for specific user:

rules_version = '2';
service cloud.firestore {
  match /databases/{database}/documents {
    match /{col}/{doc=**} {
      allow read, write: if request.auth.token.email == '[email protected]';
    }
  }
}

A more detailed example of full admin and editor access using Custom Claims:

rules_version = '2';
service cloud.firestore {
  match /databases/{database}/documents {
    match /{col}/{doc=**} {
      allow read: if hasRole(['admin','editor']);
      allow write: if hasRole(['admin']) || (col != '_CMS_' && hasRole(['editor']));
    }
    function hasRole(roles) {
      return request.auth != null && request.auth.token.get("role", null) in roles;
    }
  }
}