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

bash-conf

v0.0.2

Published

Read a simple bash config file (simple variables and values) and convert into a Javascript object.

Downloads

3

Readme

bash-conf

Read a simple bash config file (simple variables and values) and convert into a Javascript object.

This allows you to keep API keys, Database names etc out your source code and in a shareable location that both bash and node scripts can read.

Example config

It's intended to read a simple text file like this:

EMPTY_VAR=
FOO=BAR
this line will be ignored

Which has been used in a bash script like this:

# set vars
. /path/to/config/file.cfg
export FOO

Usage

var path = process.argv[ 2 ],
	BashConf = require('bash-conf'),
	bashConf = new BashConf();

bashConf
	.read( path )
	.then(function( data ) {
		console.log( 'what is foo', data.FOO );
		console.log( 'this should be empty -> [', data.EMPTY_VAR, ']' );
	})
	.catch( function( err ) {
		console.log( err );
	});

Error Handling

Lines that don't match the regex pattern are simply ignored and not parsed.

Missing config path

$ node test.js
No path supplied

Invalid config path

$ node test.js aintnofile.cfg
Could not read conf file aintnofile.cfg