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

node-file-config

v0.1.0

Published

Automatically read config from files for a project. If changes are made to the config files, a new copy of config is fetched next time.

Downloads

26

Readme

node-file-config

Automatically read config from files for a project. If changes are made to the config files, a new copy of config is fetched next time.

Usage:

var fileConfig = require("node-file-config");
var config = new fileConfig("<project_name>");
console.log(config.get(userConfig, files));
  • userConfig: Optional. If any user config is provided it will not be overridden and will just combine with the config read from the files.
  • files: Additional config files array if you want to look for config in more files.

The module checks for these config files automatically even if no additional files are provided:

  • ../../<project_folder_name>.js
  • ../<project_folder_name>.js
  • ./<project_folder_name>.js
  • ../../<project_name>.js
  • ../<project_name>.js
  • ./<project_name>.js
  • ./config.js
  • path.dirname(require.main.filename) + /<project_name>.js
  • path.dirname(require.main.filename) + /config.js
  • __dirname + <project_name>.js
  • __dirname + config.js

The priority of config is decided in the same order. But, if you specify extra config files as mentioned above, they will have top priority in the order of array provided.

All data gets combined with userConfig from all the found config files.


Example:

Files...

../../<project_name>.js

exports = module.exports = function() {
  return {
    test1: "test123", // different than user config, check below
    test2: "test456", // different than user config, check below
    test3: "test3"
  }
};

./<project_name>.js

exports = module.exports = function() {
  return {
    test3: "test10", // different than the previous config file
    test4: "test4",
    test5: "test5"
  }
};

./config.js

exports = module.exports = function() {
  return {
    test5: "test50", // different than the previous config file
    test6: "test6",
    test7: "test7"
  }
};

Let's fetch...

var fileConfig = require("node-file-config");
var config = new fileConfig("<project_name>");
console.log(config.get({test1: "test1", test2: "test2"}));

Will give...

{
  test1: "test1",
  test2: "test2",
  test3: "test3",
  test4: "test4",
  test5: "test5",
  test6: "test6",
  test7: "test7"
}

Now, let's say you made changes on the go...

../../<project_name>.js

exports = module.exports = function() {
  return {
    test1: "test123", // different than user config, check below
    test2: "test456", // different than user config, check below
    test3: "test3",
    test5: "testChanged",
    test8: "testNew"
  }
};

When fetching again next time while project is still running...

console.log(config.get({test1: "test1", test2: "test2"}));

Will give...

{
  test1: "test1",
  test2: "test2",
  test3: "test3",
  test4: "test4",
  test5: "testChanged",
  test6: "test6",
  test7: "test7",
  test8: "testNew"
}