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

@runmu.sh/brand

v0.1.0

Published

The runmu.sh look, shared by every site that wears it: the colour and type tokens, the header and footer (SiteShell), and the CSS the shell needs. No API, no session, no router.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

bitmusebitmuse

Keywords

Readme

@runmu.sh/brand

The runmu.sh look, for every site that wears it: the runmu.sh sites in clients/site (front page, /login/, /games/, /marketplace/) and the documentation at /docs/, which lives in its own public repository (runmu-sh/docs) and can only share the shell through a published package. This is that package.

| Export | Holds | |---|---| | styles/tokens.css | Every colour, the two font stacks and --gutter. The one place a colour literal may appear; clients/site/scripts/check.mjs fails a literal anywhere else, and the docs repo's check does the same. Dark only. | | styles/shell.css | What SiteShell renders needs: .wrap, .skip, the header (.nav, .brand, .nav-links, #account-slot), the footer (.foot), the .btn family and the responsive gutter. No resets, no body rule: the page brings its own (@muclient/site-ui/styles/base.css on runmu.sh, the theme on /docs/). | | SiteShell (Vue) | The header with the nav and the account slot, the page (default slot) and the footer. Props: section (home \| games \| marketplace \| docs \| login, sets aria-current), playBase (the web client's origin, default https://play.runmu.sh), siteBase (the runmu.sh origin the nav links point at; '' on runmu.sh itself). | | FONTS_HREF, fonts.json | The Google Fonts stylesheet URL (Source Sans 3, IBM Plex Mono), the sites' one third party; the JSON form is for a Node-side config (VitePress's) that cannot import TypeScript. |

The header and footer in clients/site/index.html (static HTML) must equal what SiteShell renders; clients/site/src/shell-parity.test.ts proves it and check.mjs runs it. A change to the nav is a change to both, in one commit.

Rules

  • Imports nothing but Vue (check.mjs enforces it): no API, no session, no router, no site-ui. It is published on its own and consumed by a repository that has none of those.
  • Selectors are a contract: the e2e suites (games-e2e.mjs, market-e2e.mjs) locate by .account-menu summary, a.btn-primary and friends.
  • Source is published as-is (.vue + .ts, files: ["src"]): every consumer is a Vite + Vue app that compiles SFCs, so there is no build step to keep in sync.

Publishing

npm version <patch|minor|major> -w @runmu.sh/brand in clients/, commit, then .github/workflows/publish-brand.yml (run by hand) publishes to npmjs under the public @muclient scope. The docs repo pins the version and Dependabot proposes the bump.