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 🙏

© 2026 – Pkg Stats / Ryan Hefner

fireenginecms

v1.0.16

Published

Self-hosted Firebase CMS with automatic schema detection and admin UI generation

Readme

FireEngine

Self-hosted Firebase CMS with automatic schema detection and admin UI generation. Deploy your own professional admin interface in minutes, not months.

Features

  • ⚡ Automatic schema detection from your Firestore collections
  • 🌐 Self-hosted on your own infrastructure
  • 👥 Role-based access control with granular permissions
  • 🎨 Schema customization via code configuration
  • 🔒 Multiple authentication methods
  • 🎛️ Customizable admin interface

Installation

# Using npm
npm install fireenginecms

# Using yarn
yarn add fireenginecms

Quick Start

Prerequisites:

  • Enable Firebase Authentication with Email/Password provider
  • Create a user account with the same email as ownerEmail
const express = require('express');
const fireengine = require('fireenginecms');
const app = express();

app.use('/admin', fireengine({
  adminCredentials: './firebase-admin-key.json',
  webappConfig: './firebase-config.json',
  ownerEmail: '[email protected]'
}));

app.listen(3000);

Configuration

FireEngine can be configured either through code (in your application) or environment variables - choose what suits your development workflow. When using environment variables exclusively, the config object becomes optional. All FireEngine runtime environment variables use the FIREENGINE_ prefix:

FIREENGINE_FIREBASE_PROJECT_ID=your-project-id  
FIREENGINE_FIREBASE_PRIVATE_KEY="-----BEGIN PRIVATE KEY-----..."
FIREENGINE_FIREBASE_CLIENT_EMAIL=firebase-adminsdk-abc123@project.iam.gserviceaccount.com
[email protected]

For complete documentation including deployment guides, authentication setup, and advanced configuration, visit fireengine.dev/docs.

Configuration Options

| Option | Type | Default | Description | |--------|------|---------|-------------| | adminCredentials | Object|String | - | Firebase Admin SDK credentials (object or file path) | | webappConfig | Object|String | - | Firebase web app configuration (object or file path) | | ownerEmail | String | - | Email of the admin owner | | schemaOverrides | Object | {} | Custom schema definitions | | customFields | Object | {} | Custom field type definitions | | googleMapsApiKey | String | - | API key for Google Maps integration | | googleMapsOptions | Object | {} | Google Maps configuration options | | ignoreCollections | Array | [] | Collections to ignore during auto-detection | | useFirestoreAccessRules | Boolean | false | Use Firebase security rules vs API endpoints | | firestoreDatabase | String | - | Firestore database ID (for multi-database projects) | | storageMaxUploadSize | String|Number | - | Maximum file upload size (e.g., "100MB", "5GB") |

Schema Customization

FireEngine automatically detects your Firestore collections and generates admin interfaces. You can customize these schemas:

app.use('/', fireengine({
  // ... other config
  schemaOverrides: {
    "users": {
      title: "User Management",
      titleTemplate: "${displayName} (${email})",
      fields: [
        { name: "email", type: "string", required: true },
        { name: "displayName", type: "string", required: true },
        { name: "role", type: "string", options: ["admin", "user", "moderator"] }
      ]
    }
  }
}));

Deployment

FireEngine can be deployed anywhere Node.js runs:

Express Server:

const express = require('express');
const fireengine = require('fireenginecms');

const app = express();
app.use('/', fireengine(config));
app.listen(3000);

Using Environment Variables Only:

const express = require('express');
const fireengine = require('fireenginecms');

const app = express();
app.use('/', fireengine()); // Config object is optional when using env vars
app.listen(3000);

Firebase Functions:

const functions = require('firebase-functions');
const fireengine = require('fireenginecms');

exports.admin = functions.https.onRequest(
  fireengine(config)
);

Configure and deploy.

Links

License

MIT License - see LICENSE file for details.