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

config-general

v0.2.0

Published

A Node.js version of the Perl Config::General module that attempts to be API, feature and bug compatible with the original

Downloads

8

Readme

config-general

A port to NodeJS of the Perl module Config::General

Please note that this code, while hopefully fully functional and bug-free, should be considered a late beta.

Example:

var cg = require('config-general');

var config = cg.parser( { ConfigFile: <filename> } );
var config_data = config.getall();

Yes, it really can be that simple. In fact, if you want to use the defaults for all the options, you can even write the above as:

var config = cg.parser(<filename>);

The data returned from the parsers "getall" method is a standard JavaScript Object masquerading as a hash. You can reference items in that Object as you would items in any other JavaScript object.

For more information about available options and the format of the file itself, please see the documentation of Perl's Config::General and its two sub-modules, Config::General::Extended and Config::General::Interpolated.

I have done a lot of work to make as many features of the Perl module available to users of this NodeJS module. Two features that are missing are the ability to 'tie' to a backing-store (Config::General's '-Tie' parameter) and the functional interface. The "AUTOLOAD methods" feature of Config::General is emulated, to a degree, via the use of ES6 (Harmony) Proxies. To use that feature, you must start your process with either the '--harmony-proxies' or '--harmony' flag.

Please leave information about any missing features or founds bugs on the bug-tracker provided by Github for the project.