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-config

v1.0.0

Published

Utility for working with firebase configs in different environments

Downloads

277

Readme

npm npm "Buy Me A Coffee"

firebase-config: a command-line utility for working with firebase config files.

firebase-config is a utility that lets you manage different firebase config files for different environments. It uses the value of process.env.NODE_ENV to determine the appropriate firebase config file for that enviromnent and creates a firebase.json file that is a symlink to the firebase config file for that environment.

Installing globally:

Installation via npm. If you don't have npm yet:

 curl https://npmjs.org/install.sh | sh

Once you have npm:

 npm install firebase-config -g

This will install firebase-config globally so that it may be run from the command line.

Configuring with package.json:

firebase-config uses a special firebase-config field in the package.json to resolve locations of firebase config files. For example,

"firebase-config": {
  "output": "public/",
  "configs": {
    "development": "config/firebase-dev.json",
    "production": "config/firebase-prod.json"
  }
}

You can use the "output" field to tell firebase-config where to place the generated firebase.json file. This defaults to the directory containing package.json The "configs" field is a map of values of NODE_ENV to the firebase config files to use for each environment.

Usage:

Set NODE_ENV

  • linux & mac: export NODE_ENV=production
  • windows: set NODE_ENV=production

Run firebase-config from your project directory.