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/ore-styled

v0.9.2

Published

Ore-UI styled compound components for @bedrock-core/ui

Downloads

1,173

Readme

@bedrock-core/ore-styled

Optional prebuilt Ore-UI styled compound components for @bedrock-core/ui.

Drop-in styled components that match Minecraft's modern Ore-UI look. Skip the styling boilerplate when you want consistent buttons, toggles, tabs, and cards in your addon UI.

Install

yarn add @bedrock-core/ore-styled
# or
npm install @bedrock-core/ore-styled

Components

  • Button — styled press button with variants
  • Card — content container with Ore-UI framing
  • Checkbox — boolean input with on/off textures
  • Input — text field; pressing it opens the native modal text field
  • Dropdown — selector field with a chevron; pressing it opens the native modal dropdown
  • Slider — field drawn as a track + thumb (positioned by value); pressing it opens the native modal slider
  • RadioGroup / Radio — single-select group
  • Tabs / TabList / Tab / TabPanel — tabbed navigation
  • Toggle — switch-style boolean input
  • ToggleButtonGroup / ToggleButtonItem — multi-button selector
  • Form — native modal form with styled fields (see below)
  • Divider — horizontal/vertical separator
  • ItemSlot — single inventory slot rendering an ItemStack with optional overlay texture
  • ItemContainer — grid of ItemSlot components covering a Container's slots
  • EquipmentSlots — vertical column of equipment slots (helmet → boots + offhand) from an EntityEquippableComponent
  • theme — design tokens for ad-hoc styling

Usage

import { Card, Toggle, Checkbox } from '@bedrock-core/ore-styled';
import { Text, useState } from '@bedrock-core/ui';

export const Settings = () => {
  const [enabled, setEnabled] = useState(false);
  const [accepted, setAccepted] = useState(false);

  return (
    <Card>
      <Text>{'Settings'}</Text>
      <Toggle on={enabled} onChange={setEnabled} />
      <Checkbox checked={accepted} onChange={setAccepted} label={'I agree'} />
    </Card>
  );
};

Forms

Form is a native ModalFormData-backed modal with an atomic, single-submit lifecycle: every field's value arrives once, in onSubmit, keyed by its name. Field members mirror the runtime's Form namespace but come pre-styled, and each takes a label (composed here — the runtime primitives are label-free):

  • Form.Toggle — settings-row switch
  • Form.Checkbox — boolean with on/off textures
  • Form.Radio — single-select group from options
  • Form.ToggleButton — multi-button selector from options
  • Form.Slider — track + thumb, label above
  • Form.Dropdown — native modal dropdown, label above
  • Form.Input — text field, label above
  • Form.Button — submit / exit action button (variant defaults to primary for submit, secondary for exit)

A form must declare exactly one Form.Button type="submit" (and at most one type="exit"), placed anywhere in the flow.

import { Form } from '@bedrock-core/ore-styled';
import { Text } from '@bedrock-core/ui';

export const Settings = () => (
  <Form onSubmit={(v) => { v.sound; v.volume; v.mode; }}>
    <Text>{'§lSettings'}</Text>
    <Form.Toggle   name={'sound'}  label={'Sound'} defaultValue={true} />
    <Form.Slider   name={'volume'} label={'Volume'} min={0} max={10} />
    <Form.Dropdown name={'mode'}   label={'Mode'} options={['Easy', 'Hard']} />
    <Form.Input    name={'nick'}   label={'Nickname'} />
    <Form.Button   type={'submit'} label={'Save'} />
  </Form>
);

Mix a modal <Form> and an ActionForm-style screen across separate render() calls (e.g. via navigation) — never nested.

Resource pack

These components render through the companion @bedrock-core/ui resource pack — make sure the latest .mcpack from the releases page is installed alongside your addon.

License

MIT — see the root repository.