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

hero-envy

v0.1.0

Published

Configure a Heroku environment from a file

Downloads

3

Readme

hero-envy

Configure a Heroku environment from a file

Summary

If you have run several apps from the same codebase (production, beta, dev, funsies, etc.), it can get cumbersome to manage the various environment variables. Now you can use the same .env files you'd use for local development configurations, complete with comments, and configure your remote Heroku apps.

By default, the tool gets the app name from the environment file name. So you can use awesomesauce-beta.env to configure awesomesauce-beta.herokuapp.com.

Installation

Install with npm install hero-envy -g.

Usage

The basic form takes an environment file to read:

$ heroenvy my-app-dev.env

You can override the app name:

$ heroenvy be-careful-with-production.env --app my-app-production

You can specify an account:

$ heroenvy my-app-dev.env --account personal

Sample environment file

DATABASE="my_dev_db"
NAME="My Full Name" # Comments are OK
# The line below will get ignored
#LOGGING=QUIET