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

@bedrock-oss/add-on-registry

v1.0.12

Published

A registry for Minecraft Bedrock Add-Ons and their basic meta-data. This is intended to be used by features such as WAILA-add-ons to display accurate information about packs.

Readme

Add-On Registry npm version

A registry for Minecraft Bedrock Add-Ons and their basic meta-data. This is intended to be used by features such as WAILA-Add-Ons to display accurate information about packs.

If you are an Add-On creator, you are welcome to add your pack to the registry so that it can be displayed accurately in other Add-Ons that display information about content from various Add-Ons.

Contribution

To add your project(s), create a new JSON file or edit one inside the /registry folder with the required details, and submit it via pull-request. Your pull-request will automatically merge all JSON files together into one file registry.js that is not tracked by Git but published to NPM.

Steps

  1. Create a new JSON file or edit one inside the /registry folder.

    • If you're a "new" creator, the filename should be your creator/studio name (e.g. ascent.json, spark.json).
  2. Follow the structure used in the other files. Example:

     {
         "ascent_paint": {
             "name": "Paint",
             "creator": "ASCENT"
         }
     }
  3. Commit your JSON file, then open a pull request.

Notes

  • The key should be the ID/namespace of your Add-On (the same namespace you use for blocks, entities, etc.).
  • name: Display name of your Add-On.
  • creator: Name of the creator or studio.
  • Duplicate keys are not allowed. The build will fail if a namespace is already taken.
  • Please use 4 spaces for indentation in your JSON file for consistency across all creator files.

Including it in your pack

To use the registry in your project, install it via NPM from this repository:

npm i @bedrock-oss/add-on-registry

You can now use it in your project like this:

import { Registry } from "@bedrock-oss/add-on-registry"

function getAddOnName(identifier) {
    const namespace = identifier.split(":")[0];
    const entry = Registry[namespace];
    // Use the namespace itself as fallback
    return entry ? entry.name : namespace;
}