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

local-json

v0.0.11

Published

node.js module for reading json files.

Downloads

4

Readme

local-json

node.js module for reading json files. supports async and sync modes, along with dynamically updating and caching json files without restarting the server.

  • deep-extend is used to merge json after it is processed.
  • nbqueue is used to prevent too many files from being opened at once.
  • chokidar is used for watching files and dynamically updating the server as they are changed.

install

npm install local-json

typical usage

var LocalJson = require( 'local-json' )

// default options are shown, everything is optional
var reader = new LocalJson(
  // maximum number of files allowed to be processed simultaneously in async mode
  // raise if you're on a beastly server and need more performance
  concurrency: 3,

  // working directory to read json files from
  directory: __dirname,
  
  // set true to enable updating json without restarting the server
  dynamic: true,
  
  // whether or not to log messages on json errors
  logging: true,
  
  // storage method for getting and setting parsed json data.
  // default uses standard javascript objects for cache, and is
  // generally not ideal outside of testing/development.
  storageMethod: LocalJson.StorageMethod( 'default'
    {
      // pass whatever you want to a custom storage method
      // default storage method has no options
    }
  )
)

// merge base.json, page.json, and blog.json
// .json extension is optional

// async method. if dynamic, parses json and stores the result according to the storage method.
// non-dynamic requests use require, which has built-in caching. storage methods may be extended
// to run when dynamic is disabled in the future, if needed.
reader.getData( [ 'base', 'page', 'blog' ], function ( err, data )
  {
    if ( err ) return console.log( err )
    
    // data contains object consisting of merged json files
  }
)

// sync method - data contains object consisting of merged json files.
// getDataSync does NOT utilize storage methods or caching.
// recommended only for quick prototyping and tests
var data = reader.getDataSync( [ 'base', 'page', 'blog' ] )

storage methods

local-json provides a way of using your own methods for getting/setting the parsed json data. any type of data storage system can be used. get, set, and remove functions must all be defined or it will not work properly.

currently available storage methods:

the default storage method looks like this:

// setup default storage method
// a new StorageMethod instance is passed to the function
StorageMethod.define( 'default', function ( storageMethod )
  {
    // must return a function. options parameter is optional,
    // and can be used for whatever you want.
    return function ( options )
    {
      // custom options, not used in default storage method
      // options = options || {}

      var fileData = {}

      storageMethod.get = function ( filePath, done )
      {
        if ( !fileData.hasOwnProperty( filePath ) )
        {
          return done( 'not found' )
        }

        done( null, fileData[ filePath ] )
      }

      storageMethod.set = function ( filePath, data, done )
      {
        fileData[ filePath ] = data

        done( null, data )
      }

      storageMethod.remove = function ( filePath, done )
      {
        if ( fileData.hasOwnProperty( filePath ) )
        {
          delete fileData[ filePath ]
        }

        done()
      }

      return storageMethod
    }
  }
)

license

The MIT License (MIT)

Copyright (c) 2014 Kevin von Flotow

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.