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

prerender-firebase-cache

v1.4.0

Published

Prerender plugin to cache responses in Firebase

Downloads

15

Readme

Prerender Firebase Cache plugin

Prerender plugin to cache responses in Firebase

Run this from within your Prerender server directory:

$ npm install prerender-firebase-cache --save
server.js
const prerender = require('prerender');
const firebaseCache = require('prerender-firebase-cache');
const serviceAccount = require('./serviceAccountKey.json');
const databaseURL = 'https://<yourDatabaseURL>.firebaseio.com';
const server = prerender();

server.use(firebaseCache(serviceAccount, databaseURL, '1d'));

server.start();
Test it:
curl http://localhost:3000/https://www.example.com/

A GET request will check Firebase for a cached copy. If a cached copy is found and is not expired yet, it will return that. Otherwise, it will make the request to your server and then persist the HTML to the Firebase database.

A POST request will skip the Firebase cache. It will make a request to your server and then persist the HTML to the Firebase database. The POST is meant to update the cache.

You'll need to sign up with Firebase Console and download the service account JSON file and get the database URL to pass as parameters for this plugin as example above.

Warning! Your service account JSON should be kept private and you'll be charged for all files uploaded to Firebase.

Options

The 3rd parameter is a string represents when will the cache expire. It accepts day or hour as the unit. For example 1d or 8h.

License

MIT License

Copyright (c) 2019 Johnny Bui

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.