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/server

v0.1.0

Published

The bedrock-core server meta package: one install for the cross-addon server stack

Readme

@bedrock-core/server

Logo

The meta package for the bedrock-core server stack. One dependency gets you a matching, known-good set of the server packages — each release pins the exact versions of the underlying ones, so upgrading @bedrock-core/server moves the whole stack together.

Install

yarn add @bedrock-core/server

@minecraft/server is a peer dependency (>=2.8.0) — it stays yours to pin, since the version you build against has to match the one your pack's manifest.json declares.

What you get

  • @bedrock-core/server re-exports @bedrock-core/server-runtime — the framework runtime: addon registration, the cross-addon registry, features, config, guides, translations and RPC. This is what most addons import.
  • @bedrock-core/server/sync re-exports @bedrock-core/sync — the low-level cross-addon transport (message bus, peer discovery, RPC, replicated state), for when you need to talk to it directly rather than through the runtime.

Usage

import { core } from '@bedrock-core/server';

core.register({
  creator: 'ms',
  creatorName: 'My Studio',
  pack: 'shop',
  packName: 'My Shop',
  version: '1.0.0',
});

// Only if you need the transport itself:
// import { createSync } from '@bedrock-core/server/sync';

Documentation

License

MIT