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

json-sharp

v0.1.4

Published

Process operations on pure JSON objects

Downloads

14

Readme

Build Status

json-sharp

Process operations on pure JSON objects.

How it works

JSONSharp.process clones an object and processes operations returning a modified object.

Operations are simple objects with a single property representing its name.

The operation name should be preceded by the # (sharp) symbol to avoid conflicts with real data.

The property value is processed by the operation logic using a given context.

Motivation

Some systems need slightly different configuration between environments and contexts. This technique allows to have a good degree of reuse with a simple format.

Example

Given the following object and context:

var config = {
    '#merge': [
        {debug: true, url: 'http://localhost'},
        {
            '#switch': {
                '#property': 'env',
                '#case': {
                    dev: {
                        url: 'http://dev.com/'
                    },
                    prod: {
                        url: 'http://prod.com/',
                        debug: false
                    }
                }
            }
        }
    ]
};

var context = {
    env: 'dev'
};

var devConfig = require('JSONSharp').process(config, context);

Results in the following devConfig object:

{
    debug: true, // Debug flag inherited from merging with the defaults
    url: 'http://dev.com/' // Url is replaced
}

Operations

#merge

The #merge operation takes a list of objects and deeply merges its properties using the deepmerge library.

Examples:

JSONSharp.process({'#merge': [{a: 'a'}, {b: 'b']}, {});
// ==> {a: 'a', b: 'b'}

#switch

The #switch operation works much like the switch Javascript statement, with the exception that it doesn't use a break statement.

It takes an object with the following properties:

  • #property: the property name or JSONPath to be matched for results
  • #case: an object mapping #property values to desired results
  • #case.#default: the value will be used if no matching value is found

Examples:

var switchObj = {
    '#switch': {
        '#property': 'name',
        '#case': {a: 'Prop A', '#default': 'not found'}
    }
};

JSONSharp.process(switchObj, {});
// ==> "not found"

JSONSharp.process(switchObj, {name: 'a'});
// ==> "Prop A"

JSONSharp.process(switchObj, {name: '$.a'});
// ==> "Prop A"

Property resolution

A #property starting with $. will be resolved using the JSONPath library, otherwise simple property access will be used.