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

dotenv-setup

v2.0.1

Published

The `.env` generator you can bundle with your project

Downloads

3

Readme

The .env generator you can bundle with your project

Not having the .env in git makes your life easier, but it may be confusing for new users. This package solves it. You define the variables and the user just runs a script which asks him what to fill in and then generates the .env file. Easy.

Usage

1. Add dotenv-setup to your dependencies

yarn add dotenv-setup
# OR
npm install dotenv-setup

Q: Why not CLI?
A: You can bundle it with your boilerplate this way!

2. Create your dotenv-setup configuration file (e.g. setup.js)

// setup.js contents
require('dotenv-setup')([
    {
        name: "VARIABLE_ONE",
        message: "Description for the VARIABLE_ONE",
        type: Boolean
    }, 
    {
        name: "VARIABLE_TWO",
        message: "Description for the VARIABLE_TWO",
        type: Number
    },
    {
        name: "VARIABLE_THREE",
        message: "Description for the VARIABLE_THREE",
        type: String
    }
])

3. Done! You can now use your generator!

node setup.js

Tip: You may also add it to your npm scripts!

Author

👤 DEVICARUS