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

configuration-man

v1.0.1

Published

A Laravel inspired configuration module.

Downloads

4

Readme

configuration-man

A node module, inspired by Laravel's configuration class.

The module expects a folder called config within your application root (can be changed). It looks for .json files, which represent configuration files.

Example:

  1. config/app.json
  2. config/services.json
  3. config/auth.json
  4. config/database.json
  5. config/mail.json

Install

$ npm install --save configuration-man

Include the module

const config = require('configuration-man')();

Options

You can pass the following options object to the configuration-man.

Properties

basePath -> The application root folder.

configPath -> The folder that contains the configuration files.

const config = require('configuration-man')({
    basePath: path.dirname(__filename),
    configPath: "/config/"
});

Methods

You can use the following methods with the module.

Determine if the given configuration value exists. (Note: The first word before the dot, is the json file name.)

config.has('app.env') -> Check if the configuration file app.js has a property called env.

Get the specified configuration value. (Note: The first word before the dot, is the json file name.)

config.get('app.env') -> Get the property env from the configuration file app.js.

Set a given configuration value. (Note: The first word before the dot, is the json file name.)

config.set('app.env', 'Production') -> Set the property env to Production in the configuration file app.js.

Running tests

To run test cases, execute npm test within the module folder.

License

MIT