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

figgy

v0.0.0

Published

A simple config file library

Downloads

1

Readme

Figgy

Just a simple module to do configuration files my way, without having to copy/paste from the same project hundreads of times. Not designed for any use cases other than my own.

Installation

npm install figgy

Usage

All configs are loaded in a config object stored on the figgy module.

//basic usage
var figgy = require('figgy')

var config = figgy.load('main', process.argv[2] || 'config.json')

As long as figgy.load has been run, you can use figgy.get('main') in any other module and retrieve the contents of the 'main' config

figgy.load(name, filename, chdir, filter)

Arguments

  • name : The name of the config you want to set the config to
  • filename : The filename of the config. This gets required, so any
  • chdir (optional): Chdir to the path relative to the config file. This can be useful since if you have paths in your config, they will most likely be relative to the config file itself, rather than the executable path (defaults to false)
  • filter (optional): Any post-config processing can be done in this callback

figgy.set(name, config, filter)

Arguments

  • name : The name of the config you want to set the config to
  • config : A variable which to set the config to
  • filter (optional): Any post-config processing can be done in this callback

figgy.get(name)

Returns the config associated with the name passed

Arguments:

  • name : The name of the config you want to retrieve