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

env-config-prompt

v0.3.1

Published

Environment Configuration Prompter

Downloads

3

Readme

env-config-prompt

Environment Configuration Prompter.

This module loads environment config and handles manual config prompting

install

npm install env-config-prompt

base configuration file

Create a base configuration json object file. This object can contain any depth.

detail system

The base config file have to be encoded using an internal "detail" format. Here is an example of a detail object using all detail input types.

{
    "@detail": {
        "input_type": "object",

        "port": {
            "@detail": {
                "input_type": "value",
                "type": "number",
                "required": true,
                "def": 3000
            }
        },

        "only local": {
            "@detail": {
                "input_type": "option",
                "options": {
                    "true": true,
                    "false": false
                }
            }
        },

        "cron_system": {
            "@detail": {
                "input_type": "object",

                "enabled": {
                    "@detail": {
                        "input_type": "option",
                        "options": {
                            "true": true,
                            "false": false
                        },
                        "skip_next_if": false
                    }
                },

                "timer": {
                    "@detail": {
                        "input_type": "option",
                        "reset_after_input": true,
                        "options": {
                            "minute": {
                                "by_minute": {
                                    "@detail": {
                                        "input_type": "value",
                                        "type": "number",
                                        "required": true,
                                        "def": 5
                                    }
                                }
                            },
                            "hour": {
                                "by_hours": {
                                    "@detail": {
                                        "input_type": "value",
                                        "type": "number",
                                        "required": true,
                                        "def": 1
                                    }
                                }
                            }
                        }
                    }
                }
            }
        }
    }
}

The above example will result in the following prompt sequence and its respective config file:

port (3000) : 8080
only local (true/false): false
cron_system.enabled (true/false): true
cron_system.timer (minute/hour): hour
cron_system.timer.by_hours (1) : 2
{
    "port": 8080,
    "only local": false,
    "cron_system": {
        "enabled": true,
        "timer": {
            "by_hours": 2
        }
    }
}

or

port (3000) : 
only local (true/false): true
cron_system.enabled (true/false): false
{
    "port": 3000,
    "only local": true,
    "cron_system": {
        "enabled": false
    }
}

template

In order to facilitate the creation of the base config file, some syntax sugar has been added. Here is the above base config using the template:


{
    "port": 3000,

    "only local": true,

    "cron_system": {

        "enabled": {
            "@detail": {
                "input_type": "option",
                "options": {
                    "true": true,
                    "false": false
                },
                "skip_next_if": false
            }
        },

        "timer": {
            "@detail": {
                "input_type": "option",
                "reset_after_input": true,
                "options": {
                    "minute": {"by_minute": 5},
                    "hour": {"by_hours": 5}
                    
                }
            }
        }
    }
}

usage

In order to load the configuration file, one might load the module as a method and call for it while in its script as shown here


const config_loader = require('env-config-prompt')

let config = config_loader()

option parameters

  • force_reset force reset the config file (default is false)
  • conf_file file name for final config file (default is 'config.json')
  • base_conf_file file name for the base config file (default is 'base_config.json')
  • config_title first config console title (default is 'FIRST CONFIGURATION')
  • use_config_title use a first time config title (default is true)

advices

  • add the config.json (or whatever custom filename yo want to use for the config) in your .gitignore file

LICENSE

MIT LICENSE