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

@archer-oss/dependency-checker-core

v1.1.4

Published

Core logic for data management powered by dependencies

Downloads

2

Readme

dependency-checker-core

Package for core dependency checker logic used by higher level abstractions.

Given a set of data, meta data and dependencies, this package outputs the effects of applying the dependencies on the data.

Example

const data = {
  A: {
    firstName: 'Benjamin',
    lastName: 'Test',
    age: 120,
  },
  B: {
    isCurious: true,
  },
};

const metaData = {
  A: {},
  B: {
    shouldApplyEffects: true,
  },
};

const dependencies = {
  A: [
    {
      key: 'B',
      type: 'left out for brevity',
      // data and metaData for "B"
      cond: (data, metaData) => data.isCurious && metaData.shouldApplyEffects,
      effects: {
        lastName: 'Button',
      },
    },
    {
      key: 'A',
      type: 'left out for brevity',
      // data and metaData for "A"
      cond: (data, metaData) => data.lastName === 'Button',
      effects: {
        age: 20,
      },
    },
  ],
};

The output of applying the above dependencies to the above data and meta data is the following:

const updatedData = {
  A: {
    firstName: 'Benjamin',
    lastName: 'Button',
    age: 20,
  },
  B: {
    isCurious: true,
  },
};

Dependencies

Dependency Properties

Dependencies have the following properties:

const dependencies = {
  // A list of dependencies for the item "A"
  A: [
    {
      // the key that a given item is dependent on (i.e. "A" is dependent on "B")
      key: 'B',
      // A value used for TypeScript support that gives completion for the `data` and `metaData` below
      type: 'some-type',
      // A condition that gets the data and metaData for "B"
      // If the condition evaluates to true then the effects
      // are applied, otherwise the effects are ignored
      cond: (data, metaData) => true,
      // Properties which overwrite the data for "A"
      // effects stack, so a dependency lower in the list
      // with the same effect property will take precedence
      effects: {},
    },
  ],
};

Dependency Stacking

Since the dependencies are an array, you may be wondering what happens when two dependencies that update the same data property exist. In this case, the order of the dependencies comes into play with dependencies coming later in the list taking priority.

Dependency Chaining

Complex dependency chains can be made between n-number of items. For example:

const dependencies = {
  B: [
    {
      key: 'A',
      type: 'some-type',
      cond: () => true,
      effects: {},
    },
  ],
  C: [
    {
      key: 'B',
      type: 'some-type',
      cond: () => true,
      effects: {},
    },
  ],
};

In this scenario, item "B" is dependent on item "A" and item "C" is dependent on item "B". If the item "B" dependency on item "A" evaluates to true, a recalculation of item "C" will be triggered since it's dependent on item "B".

Self Dependency

Items can be dependent on themselves which can be useful for various things such as error handling. For example:

const dependencies = {
  A: [
    {
      key: 'A',
      type: 'some-type',
      cond: (data) => data.value === "I'm invalid",
      effects: {
        error: true,
      },
    },
  ],
};

Limitations

As of today, the dependency checker does not support circular dependencies, so "A" can't be dependent on "B" and "B" can't be dependent on "A" at the same time.