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

@flowpl/jsonconfig

v1.0.1

Published

A sleek library to load and merge JSON formatted config files.

Downloads

7

Readme

features

  • load Object from a JSON file
  • explicitly reference additional files and merge contents into a single Object
  • load all files from a directory and merge their contents (conf.d style)
  • explicitly reference a directory to import files from

install

npm install git://github.com/flowpl/jsonconfig_js.git

usage

var config = require('jsonconfig_js').load('pathToFile.json');

config file syntax

plain JSON string

file1.json

{"option1": "value1"}

results in:

{"option1": "value1"}
import file

file1.json

{"option1": "value1", "imports": ["/path/to/additional_file.json"]}

additional_file.json

{"option2": "value2"}

results in:

{"option2": "value2", "option1": "value1"}
import directory

file1.json

{"option1": "value1", "imports": ["/path/to/conf.d"]}

conf.d/additional_file1.json

{"option2":"value2"}

conf.d/additional_file2.json

{"option3":"value3"}

results in:

{"option2":"value2","option3":"value3","option1":"value1"}
cascading imports

file1.json

{"option1": "value1", "imports": ["/path/to/file2.json"]}

file2.json

{"option2": "value2", "imports": ["/path/to/file3.json"]}

file3.json

{"option3": "value3", "imports": ["/path/to/file3.json"]}

results in:

{"option3":"value3","option2":"value2","option1":"value1"}

Beware: circular imports result in infinite loops

overwriting values

file1.json

{"option1": "value1", "imports": ["/path/to/file2.json", "/path/to/file3,json"]}

file2.json

{"option1": "overwritten value", "option2": "value2", "option3": "value3"}

file3.json

{"option3": "newValue3"}

results in:

{"option1":"value1", "option2": "value2", "option3": "newValue3"}

The second import overwrites the first. The third import overwrites the second. The current file always wins.

cascading imports support overwriting as well

test

npm test