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

@microbit/ui-patterns

v0.2.1

Published

Higher-level UI patterns composed from @microbit/ui primitives. Ships as source; see README for the consumption setup.

Readme

@microbit/ui-patterns

Higher-level UI patterns for micro:bit web apps, composed from @microbit/ui primitives. Where @microbit/ui provides the design-system building blocks (buttons, fields, overlays), this package holds the larger assemblies apps share — recurring page furniture built from those blocks.

What's here

  • LanguageDialog — the language settings dialog every app in the family carries: a grid of language cards (endonym over English name), split into fully/partially supported sections derived from per-language support checklists (a language with any unsupported product is partial), with a per-product support tooltip and toast, an optional preview footnote, an optional "Help translate" footer link, and a primary Close button. Selection applies immediately and the dialog closes; state stays with the app (props and callbacks only, no store). Endonyms carry lang/dir attributes — with the card's accessible name wired via aria-labelledby — so assistive tech pronounces them correctly.
  • languages — the family name-book: every language any micro:bit app lists, as { id, name, enName } with canonical BCP 47 ids (which are also the family's Crowdin codes). Apps indicate support by id — the KnownLanguageId union makes a typo or mis-cased id a compile error.
  • getDefaultLanguageId — first-run language selection: BCP 47 best-fit matching of a ?l= URL hint and the browser/OS preferences against the ids the app allows to be auto-selected. The candidate set is the app's call — pass a narrowed set where landing a user in a language silently would be wrong (e.g. incomplete native-app translations).

(<html lang> needs nothing from this package: @microbit/ui's SharedUIProvider keeps it in step with the locale automatically.)

Consumption

Like @microbit/ui, this package ships as source — TypeScript compiled and style-extracted by the consuming app's build. Set up @microbit/ui first (preset stack, styled-system alias, cascade layers — see its README), then:

  1. Install the package. @microbit/ui is a peer dependency, so both must be installed; keep them upgraded together. The peer range is deliberately *: it is the one range npm accepts both for the published prerelease versions (a normal semver range refuses to match another package's prereleases) and for the in-repo workspace copy, which sits at 0.0.0. Apps pin exact versions anyway. react-icons and react-intl are peers too, matching @microbit/ui's expectations.

  2. Add this package's sources to your Panda include, alongside the @microbit/ui glob:

    include: [
      "./src/**/*.{ts,tsx}",
      "./node_modules/@microbit/ui/src/**/*.{ts,tsx}",
      "./node_modules/@microbit/ui-patterns/src/**/*.{ts,tsx}",
    ],

    Miss the glob and the components render unstyled: Panda never sees their style calls, and there is no error.

  3. Strings: compile lang/ui.<locale>.json into your per-locale catalogs exactly as you do @microbit/ui's (message ids are namespaced ui-patterns.). English needs no catalog — components carry inline defaultMessages.

Development

Stories live in stories/ here but are rendered by the repo's Storybook harness, apps/storybook, whose config globs this package — one harness for the whole family. Run it from the repo root:

npm run storybook

npm run typecheck -w @microbit/ui-patterns generates this package's own styled-system/ output (from the same base preset) and runs tsc; npm run test -w @microbit/ui-patterns runs the vitest suite.

Releases

Create a GitHub release with a tag of the form ui-patterns-vX.Y.Z (e.g. ui-patterns-v0.1.0-alpha.1). The build workflow routes the release to this package by the tag prefix and publishes it. This package is versioned independently of @microbit/ui.

License

MIT © Micro:bit Educational Foundation and contributors.