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

v0.1.0

Published

Persisted documents for @bedrock-core: a resolver that finds where a target can hold dynamic properties, and typed collections over it

Downloads

72

Readme

@bedrock-core/db

Logo

Persisted documents on dynamic properties for @bedrock-core/server. The engine offers two ABIs for them — six methods on the world, entities and container slots; three on a block entity's component — and nothing at all on a dimension or a vanilla block; this package puts one adapter over all of it, a resolver that decides, per target, where a document can live, and typed collections on top, local by design so nothing in one reaches another realm unless the addon answers an rpc method over it.

Install

yarn add @bedrock-core/db

@minecraft/server is a peer dependency, pinned to what your manifest declares; block entities need a manifest new enough to support the block-entity component.

Usage

import { createEngineDb } from '@bedrock-core/db/minecraft';
import { schema } from '@bedrock-core/db';

const db = createEngineDb('drav0011_economy');

const balances = db.collection('balances', { schema: schema<{ gold: number; lastSeen: number }>() });

balances.for(player).get();                 // undefined until written; cached after the first read
balances.for(player).patch({ gold: 10 });   // written through, one dynamic property; merges deep
balances.for(player).subscribe(doc => hud.refresh(doc));

Documentation

https://bedrock-core.drav.dev/docs/db

License

MIT