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-core/config

v0.2.0

Published

The bedrock-core addon list + config + guide UI: one realm serves it for every registered addon

Readme

@bedrock-core/config

Logo

The shared addon list + config + guide UI for @bedrock-core/ui.

Every bedrock-core addon mounts it with one line and gets settings screens, an in-game guide and a directory of every other addon in the world — because the registry, config schemas, guides and translations all replicate over @bedrock-core/sync. Whichever realm runs the newest runtime renders the UI for all of them, so an addon shipped a year ago is served today's screens.

Install

yarn add @bedrock-core/config

It also ships inside the umbrella package as @bedrock-core/ui/config. The package depends on @bedrock-core/server-runtime for types only — no value import, so the two build and version independently.

What it gives you

  • ui(core, options?) — mounts everything: the commands, the open RPC, and this addon's place in the host election
  • Commands under your own namespace<ns>:config and <ns>:configat (read and write settings from chat, with generated autocomplete for every verb and setting), <ns>:guide, <ns>:list. Turn them off with ui(core, { commands: false })
  • Screens for free — the addon list, the scope and target pickers, the config form for a scope, a reset confirmation, and each addon's guide
  • A permission rule you can reuseisOperator, allowedScopes and clampTarget, the caller-side half of authorization (the owning addon re-checks every write)
  • App for a custom mount, registerAddonCommands for the commands alone, and CONFIG_SCOPES with the ConfigScope / EntrySchema / FlatSchemaLike types for code building its own pickers

Usage

import { core } from '@bedrock-core/server-runtime';
import { ui } from '@bedrock-core/config';
import bundle from '@bedrock-core/generated/i18n';
import guides from '@bedrock-core/generated/guides';

const config = core.register({
  creator: 'bt',
  pack: 'gc_graves',
  packName: 'Graves',
  version: '1.0.0',
  translations: bundle,
  guide: guides,
  config: { server: { keepInventory: { type: 'boolean', default: false, label: 'Keep Inventory' } } },
});

ui(core); // registers bt_gc_graves:config, :configat, :guide, :list

Call ui(core) once, after core.register().

Documentation

  • configui() and its options, every command and generated enum, the permission model, the three scopes, typed config schemas, and the API reference
  • Config in the server runtime — declaring a schema, the scope accessors, cross-addon access and authorization
  • Host election — which realm serves the UI, and why

License

MIT — see the root repository.