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

firekeys

v1.0.0

Published

Convert Firebase config from JavaScript/JSON to .env format

Downloads

128

Readme

firekeys

I got tired of copying and pasting Firebase config into my Next.js apps, so I made this small CLI. It turns your Firebase config (and service account keys) into .env format automatically.

Next.js is the supported target (e.g. NEXT_PUBLIC_FIREBASE_* for client config). If you want support for other frameworks or platforms, open an issue and we can add it.

It handles both:

  • Client config — the firebaseConfig object from the Firebase console → .env with NEXT_PUBLIC_ vars
  • Service account keys — your admin SDK JSON → FIREBASE_PROJECT_ID, FIREBASE_CLIENT_EMAIL, FIREBASE_PRIVATE_KEY

Installation

npm install -g firekeys
# or
npx firekeys

Usage

Client SDK config (JavaScript)

# From argument (use single quotes so inner " work)
firekeys 'const firebaseConfig = { apiKey: "AIza...", authDomain: "...", projectId: "...", storageBucket: "...", messagingSenderId: "...", appId: "1:..." };'

# From file
firekeys config.js

# From stdin (paste then Ctrl+D)
firekeys

# Custom output file
firekeys config.js -o .env.local

Admin SDK config (JSON)

firekeys admin-key.json --pp
cat admin-key.json | firekeys --pp

Output format

Client: NEXT_PUBLIC_FIREBASE_API_KEY, NEXT_PUBLIC_FIREBASE_AUTH_DOMAIN, etc.

Admin: FIREBASE_PROJECT_ID, FIREBASE_CLIENT_EMAIL, FIREBASE_PRIVATE_KEY

Publishing to npm

cd firebasekeys-node
npm login
npm publish

After publish, users install with: npm install -g firekeys