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

abstract-pathfinder

v0.0.1

Published

Completely agnostic A* pathfinding

Downloads

5

Readme

abstract-pathfinder

Completely agnostic A* pathfinding.

Doesn't care how your data is structured. Just implement a minimal set of accessors, and this module will apply A* to whatever data or graph you're using.

Installation:

npm i --save abstract-pathfinder

Usage:

var Pathfinder = require('abstract-pathfinder')
var finder = new Pathfinder()

// implement stuff
finder.nodeToPrimitive = function (node) { ... }
finder.getNeighbors = function (node) { ... }
finder.getMovementCost = function (nodeA, nodeB) { ... }
finder.getHeuristic = function (nodeA, nodeB) { ... }

// specify two nodes and find a path
var path = finder.findPath(startNode, endNode)

Note that node here means an whatever you're using to represent positions in the graph you're findind a path through. Nodes can be any type, as long as you implement the methods consistently.

Details:

  • nodeToPrimitive should return a string or number (uniquely) for the given node
  • getNeighbors should return an array of nodes directly accessible from the given one
  • getMovementCost should return a number for the cost of moving between neighboring nodes. Negative costs mean that movement is impossible.
  • getHeuristic should return a A* heuristic number. Typically this means a lower limit of the total cost of moving between the two (not necessarily neighboring) nodes.
  • findPath returns an array of nodes, or [] if no path was found

See the examples folder for some working demos. Example 1 uses strings for nodes; Example 2 uses objects.

By:

Copyright Andy Hall, 2016. MIT license.