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

@luolapeikko/graph-entity

v0.0.6

Published

Graph Entity service to track linked service nodes and node change events

Readme

graph-entity

Graph Entity service to track linked services and change events, idea is loosely based on Graph Database but more Entity and event driven.

Overview

Service is designed to track linked service nodes and their change events (by adding/removing nodes and edges and nodes emitting change events). This allow tracking changes as example NodeJS => Express => Logins: [User1, User2, User3] / Logouts. Or track other services like Redis, MongoDB, etc. and those relations and events.

Example

import {EventEmitter} from 'events';
import type {type GraphNodeEventMapping, type IGraphBaseEntityNode, type IGraphEventEntityNode} from '@luolapeikko/graph-entity-types';
import {GraphManager} from '@luolapeikko/graph-entity';

export const GraphTypeEnum = {
	NodeJS: 0,
	Express: 10,
	ExpressRouter: 11,
	MognoDB: 20,
	Redis: 30,
} as const;

const manager = new GraphManager<ExpressJs | NodeJsNode>();

type NodeJsNode = IGraphBaseEntityNode<typeof GraphTypeEnum.NodeJS, {version: string}>;
export const rootNodejsGraphNode: NodeJsNode = {
	nodeType: GraphTypeEnum.NodeJS,
	getNodeId: () => 'nodejs',
	getNodeProps: () => ({version: process.versions.node}),
};
manager.addNode(rootNodejsGraphNode); // add nodejs node to manager

export class ExpressJs
	extends EventEmitter<GraphNodeEventMapping>
	implements IGraphEventEntityNode<typeof GraphTypeEnum.Express, {port: string | number | undefined; status?: 'running' | 'stopped'}>
{
	public nodeType = GraphTypeEnum.Express;
	public getNodeId = () => 'express';
	private port: string;
	private status: 'running' | 'stopped' = 'stopped';
	public constructor(port: string) {
		super();
		this.port = port;
		manager.addEdge(rootNodejsGraphNode, this); // here constructor work easy way to add edge to nodejs root node
		// after start server, set status to running and notify with this.emit('nodeUpdated') event
	}
	public getNodeProps() {
		return {
			port: this.port,
			status: this.status,
		};
	}
}

// hook to manager events and output the node hierarchy structure
manager.on('graphUpdate', async (node) => {
	console.log(await manager.getNodeStructure(node));
});