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

node-quadtree

v1.0.0

Published

Native implementation of a QuadTree data structure.

Downloads

5

Readme

Native Node.JS Quadtree

A native implementation of a QuadTree for Node.JS. This was put together to be used as the backing data structure for high-performance collision detection in 2D.

The implementation is largely in pure C. Most data is allocated up front, so there are very few uses of malloc or free. The QuadTree is kept in memory as an array, so the implementation should be largely cache friendly. Further development to this will attempt to reduce use of malloc and free even further.

The API is currently very simple: when node_quadtree is required, the exported functions are QuadTree and Rect, both requiring new to create. A QuadTree object has add, which takes a Rect and any object, and intersecting, which an x, y, w, h and returns an array of objects where the rect key has the colliding rect and obj has the object associated with that rect. Rect has the attributes x, y, w, h.

Performance

Currently the set of performance tests in test.js indicate that, on average, intersection tests take 2-3 microseconds (2000-3000 nanoseconds) meaning about 333,333 intersection tests can be performed every millisecond. This scales to 1000 objects in the QuadTree spread evenly along the diagonal from the top left down to the bottom right for a 2048x2048 pixel tree. When the tree is only 1024x1024, it can take up to 16+ microseconds per intersection test, but that is due to the tree becoming tightly packed with the 1000 objects, causing each intersection test to need to iterate over a large number of items all the way at the bottom of the tree. Typical usage should not see the tree getting so tightly packed with items, and should see the 2-3 microsecond performance.

Testing for how fast adding elements is has not yet been done.

Removing items from the quadtree is not yet implemented, so there can be no performance data on it yet.