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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@giraphics/gravix-engine

v0.5.1

Published

ECS-based 3D rendering library for map and point-cloud visualisation, with a pluggable render backend

Readme

@giraphics/gravix-engine

ECS-based 3D rendering library for map and point-cloud visualisation, built on bitECS with a pluggable render backend.

Live demo · Lorenz attractor · WebGL2

GitHub’s README cannot run WebGPU, so the demo is that link, not an embedded canvas. Use a browser with WebGPU (Chrome/Edge). If it is blank, open the WebGL2 link.

Install

npm install @giraphics/gravix-engine
# plus a backend, if you want to render to a canvas:
npm install @babylonjs/core

Requires Node 20+.

Usage

import { GravixEngine } from '@giraphics/gravix-engine';
import { BabylonBackend } from '@giraphics/gravix-engine/babylon';

const engine = await GravixEngine.create(new BabylonBackend(), { canvas });
engine.start();

Headless (no browser, no GPU): pass NullBackend from the root entry instead. Polygon tessellation lives on a third entry so consumers that never draw a polygon never download earcut:

import { tessellatePolygon } from '@giraphics/gravix-engine/geo';

| Subpath | What it is for | |---|---| | @giraphics/gravix-engine | Engine, ECS, geometry, UTM, NullBackend | | @giraphics/gravix-engine/babylon | Babylon.js backend (@babylonjs/core peer) | | @giraphics/gravix-engine/geo | Polygon tessellation (earcut) |

Design

  • ECS core over bitECS. Components are created per world, never as module-scope singletons, so two worlds in one process cannot alias each other's storage.
  • Backend seam. The public API exposes API-neutral enums (PrimitiveTopology, PolygonMode, CullMode) and opaque resource handles. Babylon.js is one implementation of IRenderBackend; a headless NullBackend runs the same systems in Node with no browser and no GPU.
  • Babylon is an optional peer dependency and is never bundled. Applications choose and construct a backend; the library never imports one.
  • Scene graph. Parent/child via ChildOf, world transforms composed T * Rx * Ry * Rz * S, visibility cascading through ancestors, and disposal that tears children down with their parent.

Development

npm install
npm run typecheck
npm test
npm run build
npm run verify:pack

Smoke canvases (not published): npm -w apps/test-gravix run dev

GitHub Pages

Push main. The workflow builds the library, then the smoke app, and deploys it. Once, in the GitHub repo: Settings → Pages → Source: GitHub Actions. After the first green run the live demo URL above works.

Roadmap

  • PLAN.md — how the library was built, Phases 0–6. Complete.
  • MAP-VIEWER-PLAN.md — Map Viewer capabilities: spatial indexing, A* navigation, grouped draw calls, viewport streaming with LOD, crowd simulation, procedural sky. M1–M7 landed.

License

MIT