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

pulsar-pathfinding

v2.1.1

Published

implementation of Greedy Best-First pathfinding

Downloads

7

Readme

Build Status

README IN PROGRESS

npm install pulsar-pathfinding

1: Creating the Grid.

This represents an abstract mathematical graph of nodes implemented as NavigatorTile. It may have any width and height as a constructor argument, and it defaults to {width: 10, height: 10}.

import { Grid } from 'pulsar-pathfinding';
const grid: Grid = new Grid({width: 10, height: 10});

2: Accessing NavigatorTile on the grid

NavigatorTile are stored by the Grid and can be accessed either by grid coordinates

const begin: NavigatorTile = grid.findTile({x: 0, y: 0});
const end: NavigatorTile = grid.findTile({x: 9, y: 9});

or randomly:

const randomTile: NavigatorTile = grid.randomTile();         // any possible tile
const randomFreeTile: NavigatorTile = grid.randomFreeTile(); // only tiles that are not obstacles

3: Creating Obstacles.

Obstacles can be added and removed with the add(tile), remove(tile) methods on grid.obstacles

  const tile: NavigatorTile = grid.findTile({x: 0, y: 0});
  grid.obstacles.add(tile); // tile.isObstacle = true
  grid.obstacles.remove(tile); // tile.isObstacle = false

4: Creating a Navigator.

This is the object that traverses the Grid you created. It requires the following as constructor arguments: a grid, a begin tile and an end tile.

import { Navigator } from 'pulsar-pathfinding';

const grid: Grid = new Grid({width: 10, height: 10});

const begin: NavigatorTile = grid.findTile({x: 1, y: 1});
const end: NavigatorTile = grid.findTile({x: 9, y: 9});

const navigator: Navigator = new Navigator({grid, begin, end});

Optionally, Navigator may receive two callback functions, in the form of onExplore and onComplete.
and an optional maxSteps parameter.

const navigator: Navigator = new Navigator({
  grid,
  begin,
  end,
  onExplore: (NavigatorTile) => {
    // NavigatorTile
  },
  onComplete: (NavigatorTileArray) => {
    // NavigatorTile[]
  },
  maxSteps: 10,
});

onExplore(NavigatorTile) will be called for each NavigatorTile that the Navigator explores
onComplete(NavigatorTile[]) will be called with the array of NavigatorTiles in the shortest path that the Navigator found

The Navigator explores multiple possible tiles until it finds the shortest route.

If No path is found, onComplete will return an empty Array

Once the navigator is created, we now call the start method.
The resulting path (a NavigatorTile array), is stored in the path property.

navigator.start();
draw(navigator.path);