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

combine-json

v1.0.0

Published

Combines a group of json files and folders into an object

Downloads

212

Readme

Combine-JSON logo

Build Status GitHub issues Version Downloads MIT License

Combine-JSON

This module (and CLI) allows you to create one JSON file from smaller files stored in a directory hierarchy. The smaller files can be in JSON (default) or any other format like JSON5 or YAML or even INI (custom parser).

Why? Sometimes you have a huge JSON file with lots of nested objects but you want to break it into a file hierarchy because:

  • It is easier to browse to a particular section
  • It is easier to understand the shape of the data structure at a glance
  • Editing any subparts of the document leads to cleaner individual git history and diffs

Example

Given this JSON file:

my-data.json
{
    "name": "Alex Ewerlöf",
        "address": {
        "street": "Hittepågatan 13",
        "city": "Stockholm",
        "country": "Sweden",
        "zip": "11122"
    },
    "todos": [
        {
            "id": 1,
            "title": "document the module",
        },
        {
            "id": 2,
            "title": "write some tests",
        },
        {
            "id": 3,
            "title": "publish it for good",
        }
    ]
}

We can break it into several files like this:

my-data/name.json
"Alex Ewerlöf"

(Yes that's a perfectly valid input to JSON.parse())

my-data/address.json
{
    "street": "Hittepågatan 13",
    "city": "Stockholm",
    "country": "Sweden",
    "zip": "11122"
}
my-data/todos.json
[
    {
        "id": 1,
        "title": "document the module",
    },
    {
        "id": 2,
        "title": "write some tests",
    },
    {
        "id": 3,
        "title": "publish it for good",
    }
]

You can write that array of objects into files as well:

my-data/todos/0.json
{
    "id": 1,
    "title": "document the module",
}
my-data/todos/1.json
{
    "id": 2,
    "title": "write some tests",
}
my-data/todos/2.json
{
    "id": 3,
    "title": "publish it for good",
}

So the file structure looks like this:

my-data/
    |____name.json
    |____address.json
    |____todos/
        |____0.json
        |____1.json
        |____2.json

Of course you can have directories for array elements as well:

my-data/
    |____name.json
    |____address.json
    |____todos/
        |____0/
        |    |____id.json
        |    |____title.json
        |____1.json
        |____2.json

Take a look at the test/my-data directory to see it in action.

Usage

$ npm i combine-json

const { combine } = require('combine-json')

const myBigJsonObject = await combine('path/to/the/root/dir')

API

See the js docs online.

Known limitations

  • In the current implementation we ignore any directory starting with ..
  • If a folder contains subfolders or files that look like numbers, an array will be created instead of an object.

CLI

You can use the CLI for testing what the output may look like.

$ npx combine-json test/my-data/
{
    "address": {
        "street": "Hittepågatan 13",
        "city": "Stockholm",
        "country": "Sweden",
        "zip": "11122"
    },
    "name": "Alex Ewerlöf",
    "todos": [
        {
            "id": 1,
            "title": "document the module"
        },
        {
            "id": 2,
            "title": "write some tests"
        },
        {
            "id": 3,
            "title": "publish it for good"
        }
    ]
}

Made in Sweden by @alexewerlof