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

@prometheus-ags/prometheus-entity-management

v4.0.2

Published

Compatibility alias for @prometheus-ags/entity-graph-react. The React bindings publish under that name; this package re-exports them so existing installs keep resolving.

Readme

@prometheus-ags/prometheus-entity-management

This package is a compatibility alias. Install @prometheus-ags/entity-graph-react instead.

npm install @prometheus-ags/entity-graph-react

Why the name changed

Every framework binding in this workspace is named after the framework it binds:

| Package | Framework | |---|---| | @prometheus-ags/entity-graph-react | React | | @prometheus-ags/entity-graph-solid | Solid | | @prometheus-ags/entity-graph-svelte | Svelte | | @prometheus-ags/entity-graph-alpine | Alpine | | @prometheus-ags/entity-graph-htmx | htmx | | @prometheus-ags/entity-graph-tauri | Tauri | | @prometheus-ags/entity-graph-web-components | Web Components |

React was the exception. Its source has always lived in packages/entity-graph-react/, but it published under the product name — so the one binding most people reach for first was the one whose install name could not be guessed from its role, and whose directory name did not match the package it produced.

That is now fixed. The directory and the package name agree.

Nothing breaks

This package still publishes, still carries the same version as the rest of the release group, and re-exports the React binding verbatim — all three entrypoints:

import { useEntity } from "@prometheus-ags/prometheus-entity-management";
import { … }         from "@prometheus-ags/prometheus-entity-management/devtools";
import                     "@prometheus-ags/prometheus-entity-management/devtools/auto";

Each forwards to the matching @prometheus-ags/entity-graph-react entrypoint. Existing code keeps working with no edit.

Migrating

Change the dependency and the import specifier. The exported API is identical — this package adds nothing and removes nothing.

- "@prometheus-ags/prometheus-entity-management": "^3.2.0"
+ "@prometheus-ags/entity-graph-react": "^3.2.0"
- import { useEntity } from "@prometheus-ags/prometheus-entity-management";
+ import { useEntity } from "@prometheus-ags/entity-graph-react";

Licence

MIT