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

treeresolver

v2.1.1

Published

TreeResolver is a dependency resolution library, made to resolve dependencies optimally whilst detecting unresolvable or circular dependencies.

Downloads

2

Readme

TreeResolver

TreeResolver is dependency resolution library, made to resolve dependencies optimally whilst detecting unresolvable or circular dependencies.

TreeResolver itself provides single-parent dependency resolution, whilst DepResolver provides multi-parent dependency resolution.

Written in TypeScript.

license

MIT license; see ./LICENSE

documentation

Automatically generated documentation is available in /docs/.

TreeResolver - Single-parent dependency resolution

Usage is fairly simple. Create a new TreeResolver instance, add new instances by declaring their names, dependencies, and optional dependencies, and then build the relationship tree. The result should be a well-structured dependency tree free of unresolvable and circular dependencies.

import { TreeResolver } from 'TreeResolver'
const tree = new TreeResolver()

(async () => {
  tree.addInstance('node 1')
  tree.addInstance('node 2', 'node 1')
  tree.addInstance('node 3', 'node 4') // node 4 does not exist...
  tree.addInstance('node 5', 'node 2')

  const res = await tree.build()
  console.dir(res)
})()
/*
> { nodes:
   { 'node 1':
      { name: 'node 1',
        parent: undefined,
        parentNode: null,
        rootNode: null,
        children: [Object],
        allDescendants: [Object],
        allAncestors: {} } },
  nodeList:
   { 'node 1':
      { name: 'node 1',
        parent: undefined,
        parentNode: null,
        rootNode: null,
        children: [Object],
        allDescendants: [Object],
        allAncestors: {} },
     'node 2':
      { name: 'node 2',
        parent: 'node 1',
        parentNode: [Object],
        rootNode: [Object],
        children: [Object],
        allDescendants: [Object],
        allAncestors: [Object] },
     'node 3':
      { name: 'node 3',
        parent: 'node 4',
        parentNode: null,
        rootNode: null,
        children: {},
        allDescendants: {},
        allAncestors: {} },
     'node 5':
      { name: 'node 5',
        parent: 'node 2',
        parentNode: [Object],
        rootNode: [Object],
        children: {},
        allDescendants: {},
        allAncestors: [Object] } },
  unlinkedNodes:
   [ { name: 'node 3',
       parent: 'node 4',
       parentNode: null,
       rootNode: null,
       children: {},
       allDescendants: {},
       allAncestors: {} } ] }
 */

// nodes will contain a hierarchial tree map, keyed by name of the node
// nodeList will contain ALL nodes that were able to be mapped, keyed by the name of the node
// unlinkedNodes will contain an array of all nodes which could not be mapped, such as if
//   they had unresolvable dependencies or a circular dependency.

DepResolver - Multi-parent dependency resolution

Usage is fairly simple. Create a new DepResolver instance, add new instances by declaring their names, dependencies, and optional dependencies, and then build the relationship tree. The result should be a well-structured dependency tree free of unresolvable and circular dependencies.

import { DepResolver } from 'DepResolver'
const tree = new DepResolver()

(async () => {
  tree.addInstance('node 1')
  tree.addInstance('node 2', [], ['node 4']) // has an optional dependency on "node 4", which will not exist
  tree.addInstance('node 3', ['node 2'])
  tree.addInstance('node 5', ['node 1', 'node 2', 'node 3'])

  const res = await tree.build()
  console.dir(res)
})()

/*
> { nodes:
   { 'node 1':
      { name: 'node 1',
        parents: {},
        children: [Object],
        allDescendants: [Object],
        allAncestors: {},
        _parentNames: [],
        _optParentNames: [] },
     'node 2':
      { name: 'node 2',
        parents: {},
        children: [Object],
        allDescendants: [Object],
        allAncestors: {},
        _parentNames: [],
        _optParentNames: [Array] } },
  nodeList:
   { 'node 1':
      { name: 'node 1',
        parents: {},
        children: [Object],
        allDescendants: [Object],
        allAncestors: {},
        _parentNames: [],
        _optParentNames: [] },
     'node 2':
      { name: 'node 2',
        parents: {},
        children: [Object],
        allDescendants: [Object],
        allAncestors: {},
        _parentNames: [],
        _optParentNames: [Array] },
     'node 3':
      { name: 'node 3',
        parents: [Object],
        children: [Object],
        allDescendants: [Object],
        allAncestors: [Object],
        _parentNames: [Array],
        _optParentNames: [] },
     'node 5':
      { name: 'node 5',
        parents: [Object],
        children: {},
        allDescendants: {},
        allAncestors: [Object],
        _parentNames: [Array],
        _optParentNames: [] } },
  unlinkedNodes: [] }
 */

// upon closer inspection of the tree, you'll notice that the node
//   for 'node 2' contains its appropriate descendants in correct lineage, along with others.
//
// nodes will contain a hierarchial tree map, keyed by name of the node
// nodeList will contain ALL nodes that were able to be mapped, keyed by the name of the node
// unlinkedNodes will contain an array of all nodes which could not be mapped, such as if
//   they had unresolvable dependencies or a circular dependency.

tests

use yarn test to run unit tests