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

generate-env

v2.0.4

Published

With [npm](https://npmjs.org) do: ``` npm i -g generate-env ```

Downloads

27

Readme

generate-env

install

With npm do:

npm i -g  generate-env

How to use

At the env.config.json file level type generatenv + branch name + file name

Branches accepted prod, dev, qa

Example

    generatenv dev env.config.json

File Config

The file name can be anything as long as it is in json format

If you do not set a file in the command, it will be used env.config.json

File Format

Use V1 :

{
    "version":1,
    "file":".env",
    "airtableToken":"Airtable Key",
    "airtableUrl":"Airtable Api url",

    "airtableBaseDev":"Airtable base DEV",
    "airtableBaseProd":"Airtable base Prod",
    "airtableBaseQa":"Airtable base QA",

    "tableEnvs":"Name of the table where you save the env",
    "env":[
        {
            "identifier":"Identifier of your variable",
            "varName":"Variable name"},
    ]
}

Use V2 :

{
    "version":1,
    "file":".env",
    "airtableToken":"Airtable Key",
    "airtableUrl":"Airtable Api url",

    "airtableBaseDev":"Airtable base DEV",
    "airtableBaseProd":"Airtable base Prod",
    "airtableBaseQa":"Airtable base QA",

    "tableEnvs":"Name of the table where you save the env",
    "tableApplications":"Name of the table where you save your applications",
    "applicationName":"Name of the application to create the env",
    "env":[]
}

To add prefix:

{
    "prefix": true,
    "namePrefix":"MY_PREFIX",
}

Update:

V: 2.0.0 Add new functionalities and configuration formats

license

MIT