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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@phinxlab/config-public

v0.0.3

Published

## Configuration file

Downloads

235

Readme

Config definition

Configuration file

The file configuration will be looked at the CWD (Command working directory) or into it parents directory. It will look for the file name environment.json and it will have the following format:

environment.json

type Enviroment={
    config:string,
    mode:'file'|'proxy',
    proxy?:string,
    cwd?:string,
    path?:string,
    bbd?:string
}

Attributes specification

  • config Will define the folder inside de config folder where the configuration files will be defined. Traditional configurations are:

    • dev => Development environment
    • qa => Quality Assurance environment
    • prod => Production environment
  • mode Will determine the mode that the configuration will work. Posible options are:

    • file => The platform will automatically look for the files at the defined folder. See config.
    • proxy => It will look for a javascript file that will manage the loding of configuration. See proxy
  • path This will define the default path to he configuration enviroments. By default it will be targeted to CWD()../config. So be aware that if you change the CWD() you will also need to specified this parameters in order to make the platform work.

  • proxy This attribute is mandatory when you specified the 'proxy' mode. It will aim to the .js file that will be in charge of loading the configuration. The platform will look for the corresponding file inside the enviroment specified on config. See config. The file will have to exports a function with the signature:


(path:string,config:string)=>any

Since it will be a javascript file it should be defined like this:


function proxyLoader(path,config) {
    const configObject = require(config);
    //Mofify whatever you need on your base config
    //configObject.password = env.password
    return configObject;
}
module.exports = proxyLoader;
  • cwd In case that you decided to run the application from a different directory where the initiation is, you will need to specified the correct directories where the platform will have to search for files.

  • bbd This is the directory where the base code is located. In case that you changed the cwd, you will need to specified in order to find the base code.

Glossary

  • cwd Command Working Directory

  • bbd Build Base Directory