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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@sim.perelli/dot-conf

v0.2.2

Published

Simple .conf file parser for Nodejs

Downloads

4

Readme

dot-conf

Simple .conf file parser for Nodejs

This is mostly done with educational purposes.

npm install @sim.perelli/dot-conf

Let's write a simple configuration file

# main.conf
# this is a comment 
log_level = debug

server_name = _hostname_ # this is a symbol

# this is a namespace
@database
username = alfred # this is an inline comment
host = _localhost_
database = wayne_mansion

dot-conf will try its best to retrieve all the configuration files and serve them in a useful way

// somewhere else
const conf = await dotConf('main.conf')

conf('log_level')
// debug

conf('server_name')
// nightwing01.batcave.com

conf('database.username')
// 'alfred'

conf('mislept.or.undefined')
// undefined

conf('*')
// { log_level: 'warn', database: { username: 'alfred' ...

conf('database')
// { host: '127.0.0.1', username: 'alfred' ...

If you're organizing your application in submodules and don't feel like letting know the persistence module what an eventbus or an email server are, you can always detach a namespace from the main conf

const databaseConf = conf.detach('database')

//somewhere in the persistence module
const username = databaseConf('username')

Maybe you would like to define default values for missing configuration variables

const defaultTo = {
    log_level: 'info',
    server_name: 'nightwing01.batcave.com'
}

const conf = dotConf('main.conf',{ defaultTo })

Ehy what is this symbol thingy?

// some.conf
server_name = _hostname_
timeout = _timeout_

dot-conf let's you define placeholders (sorrounded by _) to access dynamically computed or very common values

// a symbol is essentially a function
const symbols = {
    timeout: () => 5*1000
}

const conf = dotConf('main.file', { symbols })

Any suggestion is of course very welcome.