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

@algolia/json-stream-analyzer

v1.0.0-beta.3

Published

A library to analyze JSON streams and find structural issues in the stream's schema

Downloads

1,060

Readme

json-stream-analyzer

A library to analyze JSON streams and find structural issues in the stream's schema

Disclaimer

This tool is currently designed for internal use only. There is no guarantee on maintenance, or stability, of the API of the tool. It may change at any point, without warning, and without following proper semver.

Standard usage

import { SimpleTagModel } from '@algolia/json-stream-analyzer/models';

// this will build a model that can keep track of the schema of a stream 
// and keep one tag for each diverging element of the schema
const model = new SimpleTagModel({
  tag: (record) => record.objectID
});

const records = [
  {
    objectID: 1,
    title: 'How to build a performant library?',
    prices: {
      hardcover: 52,
      ebook: 10,
    },
  },
  {
    objectID: 3,
    title: 'Mastering the art of example in 12 steps',
    description:
      'The description and prices.hardcover fields are missing in some records and prices.ebook has multiple types',
    prices: {
      ebook: '10$',
    },
  },
];

// feed the records to the model
records.forEach(model.addToModel);

// get the schema of the model
console.log(JSON.stringify(model.schema, null, 2));
/*
{
  "counter": 2,
  "tag": 1,
  "type": "Object",
  "schema": {
    "objectID": {
      "counter": 2,
      "tag": 1,
      "type": "Number"
    },
    "title": {
      "counter": 2,
      "tag": 1,
      "type": "String"
    },
    "description": {
      "counter": 2,
      "type": "Union",
      "types": {
        "Missing": {
          "counter": 1,
          "tag": 1,
          "type": "Missing"
        },
        "String": {
          "counter": 1,
          "tag": 3,
          "type": "String"
        }
      }
    },
    "prices": {
      "counter": 2,
      "tag": 1,
      "type": "Object",
      "schema": {
        "ebook": {
          "counter": 2,
          "type": "Union",
          "types": {
            "Number": {
              "counter": 1,
              "tag": 1,
              "type": "Number"
            },
            "String": {
              "counter": 1,
              "tag": 3,
              "type": "String"
            }
          }
        },
        "hardcover": {
          "counter": 2,
          "type": "Union",
          "types": {
            "Number": {
              "counter": 1,
              "tag": 1,
              "type": "Number"
            },
            "Missing": {
              "counter": 1,
              "tag": 3,
              "type": "Missing"
            }
          }
        }
      }
    }
  }
}
*/

// immediately find issues within the schema
const diagnostics = model.diagnose();
/*
[
  {
    id: 'missing',
    title: 'Missing Data',
    type: 'Union',
    path: [ 'description' ],
    affected: 1,
    tag: 1
  },
  {
    id: 'healthy',
    title: 'Healthy Records',
    type: 'Union',
    path: [ 'description' ],
    affected: 1,
    tag: 3
  },
  {
    id: 'inconsistentType',
    title: 'Inconsistent Type (String instead of Number)',
    type: 'Union',
    path: [ 'prices', 'ebook' ],
    affected: 1,
    tag: 3
  },
  {
    id: 'healthy',
    title: 'Healthy Records',
    type: 'Union',
    path: [ 'prices', 'ebook' ],
    affected: 1,
    tag: 1
  },
  {
    id: 'missing',
    title: 'Missing Data',
    type: 'Union',
    path: [ 'prices', 'hardcover' ],
    affected: 1,
    tag: 3
  },
  {
    id: 'healthy',
    title: 'Healthy Records',
    type: 'Union',
    path: [ 'prices', 'hardcover' ],
    affected: 1,
    tag: 1
  }
]
*/

// find issues within record based on a schema
model.diagnoseRecord({
  objectID: 1,
  title: 'How to build a performant library?',
  prices: {
    hardcover: 52,
    ebook: 10,
  },
});
/*
[
  {
    id: 'missing',
    title: 'Missing Data',
    type: 'Union',
    path: [ 'description' ],
    affected: 2,
    tag: 1
  }
]
*/