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-partial

v1.0.0

Published

Parses a json file looking for partials. If found the partial is read and applied to the json file. On exit saves the json with the provided output name.

Downloads

10

Readme

json-partial

This module will allow to use json "partials" and expand them into another json file. Sometimes you have one or more json snippets and you may want to use them to build a bigger json file. One example is when you are using json to generate templates with handlebars or mustache.

Installation

npm install json-partial

Usage

Suppose you have a JSON snippet that is repeated almost without change in several places of a large JSON file.

{
    "charRemaining": "50",
    "counterText": "characters remaining",
    "fieldName": "customerName",
    "fieldSize": "large",
    "labelPosition": "",
    "labelText": "Customer Name",
    "maxLength": "50",
    "placeHolder": "Enter customer name",
    "value": ""
}

You want to use almost the same values in two places:

{
    "userName": {
        "charRemaining": "50",
        "counterText": "characters remaining",
        "fieldName": "userName",
        "fieldSize": "large",
        "labelPosition": "",
        "labelText": "User Name",
        "maxLength": "50",
        "placeHolder": "enter user name",
        "value": ""
    },
    "password": {
        "charRemaining": "50",
        "counterText": "characters remaining",
        "fieldName": "password",
        "fieldSize": "large",
        "labelPosition": "",
        "labelText": "Password",
        "maxLength": "50",
        "placeHolder": "enter password",
        "value": "",
        "inputType": "password"
    }
}

With json-partial you can rewrite the file like this:

{
    "jsonx": [
        {
            "file": "bar.json",
            "field": "userName",
            "data": {
                "fieldName": "userName",
                "labelText": "User Name",
                "placeHolder": "enter user name"
            }
        },
        {
            "file": "bar.json",
            "field": "password",
            "data": {
                "fieldName": "password",
                "labelText": "Password",
                "placeHolder": "enter password",
                "inputType": "password"
            }
        }
    ]
}

You will have several advantages:

  1. The file is cleaner and only the data that changes is required
  2. You will need to modify only one instance of the snippet in case of a change or bugs