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

react-cms-firestore

v1.7.9

Published

Dependency-inject CMS data into any react component from the Firestore

Downloads

16

Readme

react-cms-firestore

Wrap your component in withCms to have props.cms injected into your components.

CMS data is downloaded from the Firestore.

the second argument to withCms defines the CMS entries injected into the component.

Import looks like:

import {withCms} from "react-cms-firestore";

Usage often looks like this:

export default withCms(MyScreen, 'MyScreenData');

or

export default withCms(MyComponent, ['entry1', 'entry2']);

Then the data can be accessed like:

const {cms} = props;
const {footerCms, headerCms} = cms;
const {footerTitle} = footerCms;
const {headerLogoUrl} = headerCms;
...

Placeholder Component

There is a optional third parameter which styles a default placeholder while the data is loading. It may look like this:

export default withCms(MyComponent, 'myCmsData', {width: 200, height:100});

The possible style values are: width, height, padding, paddingTop, paddingRight, paddingBottom, paddingLeft, radius, and test.

test forces the placeholder state for easy testing.

Initialization

Add a collection called cms to your Firestore. Add a collection called cms-editor to your Firestore.

####Security Rules Users with the role of admin or cmsEditor can update cms. Everyone can read cms.

Use firebase-roles package to set up initial roles.

function isCmsEditor() {
  return request.auth != null 
    && request.auth.token != null 
    && (
    request.auth.token.admin == true || 
    request.auth.token.cmsEditor == true
    );
}

match /cms/{id} {
  allow read: if true;
  allow write: if isCmsEditor();
}

match /cms-editor/{id} {
  allow read: if isCmsEditor();
  allow write: if isCmsEditor();
}

The Firestore needs to be initialized in the code before withCms is used.

For Developer

Remember to npm run build before deploying.