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

find-cycle

v1.1.0

Published

find and identify a cycle in a directed graph

Downloads

14,416

Readme

find-cycle

Build Status Coverage Status semantic-release Commitizen friendly

Searches for a cycle in a directed graph, and tells you the nodes in the first cycle it finds. Should work on your existing data structures without conversion, because it operates on Iterables and a getConnectedNodes adapter function that you provide.

The implementation is a depth-first search using a stack instead of recursion, so it's not limited by the maximum call stack size.

Compatibility

Your environment must support Set, Map, and Symbol.iterator natively or via a polyfill.

Node: 4+

Installation

npm install --save find-cycle

API

findDirectedCycle(startNodes, getConnectedNodes)

const findDirectedCycle = require('find-cycle/directed')

Arguments

startNodes: Iterable<Node>

The nodes to start the search from. Your nodes may be of any primitive or object type besides null or undefined.

getConnectedNodes: (node: Node) => ?(Iterator<Node> | Iterable<Node>)

Given a node in your directed graph, return the nodes connected to it as an Iterator or Iterable. You may return null or undefined if there are no connected nodes.

Returns: ?Array<Node>

An array of nodes in the first cycle found, if any, including each node in the cycle only once.

Examples

With Arrays

const findCycle = require('find-cycle/directed')

const edges = {
  1: [2],
  2: [3],
  3: [4],
  4: [2, 5],
  5: [3],
  7: [8, 9],
  8: [1],
  9: [10, 11],
  10: [11],
  11: [9, 8],
}

const startNodes = [1]
const getConnectedNodes = (node) => edges[node]

expect(findCycle(startNodes, getConnectedNodes)).to.deep.equal([2, 3, 4])

With Sets/Maps

const findCycle = require('find-cycle/directed'
const edges = new Map([
  [1, new Set([2])],
  [2, new Set([3])],
  [3, new Set([4])],
  [4, new Set([2, 5])],
  [5, new Set([3])],
  [7, new Set([8, 9])],
  [8, new Set([1])],
  [9, new Set([10, 11])],
  [10, new Set([11])],
  [11, new Set([9, 8])],
])

const startNodes = new Set([1])
const getConnectedNodes = node => edges.get(node)

expect(findCycle(startNodes, getConnectedNodes)).to.deep.equal([2, 3, 4])