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

data-comparer

v1.0.3

Published

comparing data structure between different systems

Downloads

4

Readme

#Data Comparer Comparing data easily from the same api of different systems (useful after migrations).

Install

npm i data-comparer

Usage

import {compareSysData, Validator} from "data-comparer";

// Lets say we have a class to wrap my system's api, customizable to different environments
class MySys {
    public name: string;

    constructor(private env: number) {
        this.name = `sys ${this.env}`;
    }

    // We can query the data using an async api method.
    public async getInfo() {
        return this.env;
    }
}

// Lets define our relevant environments
const mySystems = [
    new MySys(1),
    new MySys(1),
    new MySys(1),
    new MySys(3),
    new MySys(5),
];

console.log(`~~~ Example ~~~`);
(async() => {

    console.log('==== via class:');
    // Create a validator for our tested systems.
    const validator = new Validator<MySys>(mySystems);

    // Now validating with...
    let res = await validator.validate<number>({
        query: sys => sys.getInfo(), // How we query each system (supports promises)
        compare: (d1, d2) => ({success: d1 == d2, delta: d1 - d2}), // How we compare two sets of system data
        strategy: 'mesh' // The compare strategy - more later
    });

    console.log(res.queryErrors); // Errors from querying data
    console.log(res.results); // Comparison results



    console.log('==== comparing via function:');
    res = await compareSysData<MySys, number>(
        mySystems, // Our tested api wrappers
        sys => sys.getInfo(), // How we query each system (supports promises)
        (d1, d2) => ({success: d1 == d2, delta: d1 - d2}), // How we compare two sets of system data
        'linear'
    );

    console.log(res.results);
})();

###Compare Strategies

  • linear: sys1 with sys2, sys2 with sys3, sys3 with sys4, etc.
  • mesh: each system with each other system.
  • or just send a custom function from type:
export type CompareStrategyFn<T extends System, D> = (datas: Map<T, D>, compare: CompareFn<D>) => CompareInfo<T>[];
export interface CompareInfo<T extends System> {
    sys1 : T,
    sys2 : T,
    result : CompareResult|Promise<CompareResult>
}
export interface CompareResult {
    success: boolean;
}

##Running the example After cloning the repo',

npm i && npm start

for running the tests

npm test