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

leanconf

v0.2.1

Published

Configuration without brackets, quotes or escaping, using just 2 markup characters

Downloads

11

Readme

leanconf

Build Status

Configuration without brackets, quotes or escaping, using just 2 markup characters:

  • the key/value separator :
  • the comment character #

Indented whitespace controls nesting and primitive data types are inferred.

example

# shop.conf
name: dizzib's corner shop: Leeds, Yorkshire

patrons:
  alice:
    cash: 5.03
  bob:
    credit: 10.00

fruits          # omit key/val separator to parse immediate children to an array
  apples
    Braeburn
    Cox's       # omit key/val separator to parse as a value
    Royal Gala
  banana
  orange:
    special: true
    stock: 17

node.js code:

var conf = require('fs').readFileSync('shop.conf'});
var obj = require('leanconf').parse(conf);
console.log(require('util').inspect(obj, {depth:null}));

output:

{ name: 'dizzib\'s corner shop: Leeds, Yorkshire',
  patrons: { alice: { cash: 5.03 }, bob: { credit: 10 } },
  fruits:
   [ { apples: [ 'Braeburn', 'Cox\'s', 'Royal Gala' ] },
     'banana',
     { orange: { special: true, stock: 17 } } ] }

methods

var leanconf = require('leanconf');

var obj = leanconf.parse(conf, opts)

Parse configuration string conf returning object obj.

Set opts.asArray to return top-level items in an array (default is false).

Set opts.comment to change the comment character (default is #). Keys or values cannot contain this character. Set opts.sep to change the key/value separator (default is :).

var val = leanconf.value-parser(raw)

This function parses a raw value-string to the most appropriate data type of boolean, floating-point number, integer, null or string. Don't call this directly, rather replace or wrap it if you want to alter the default behaviour.

install

$ npm install leanconf

developer build and run

$ git clone --branch=dev https://github.com/dizzib/leanconf.git
$ cd leanconf
$ npm install     # install dependencies
$ npm test        # build all and run tests
$ npm start       # start the task runner

license

MIT