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

@oc-mui/ui

v2.0.1

Published

React UI component library (shadcn/ui + Tailwind) for the Opencast Management UI and its plugins.

Readme

@oc-mui/ui

Shared component library built on Tailwind CSS v4, Radix UI primitives (via shadcn/ui) and @dnd-kit for drag-and-drop. Atomic components (Button, Card, Input, …) plus composed building blocks (app shell, datatable, metadata fields, ACL editor, date picker, sortable list, …).

This is the only place plugins should source UI components — the Theme Contract guarantees consistent styling, and bundling your own shadcn copies breaks org theming.

Usage

import { Button, Card, CardContent } from "@oc-mui/ui/components";
import { cn } from "@oc-mui/ui/lib/utils";
import { Home, Video } from "@oc-mui/ui/components/icons";

<Card className={cn("bg-card", className)}>
  <CardContent>
    <Button>Save</Button>
  </CardContent>
</Card>;

Plugin authors import from the subpath exports — never the package root — to keep the bundle tree-shakeable:

| Subpath | What it provides | |---------|------------------| | @oc-mui/ui/components | Atomic + composed components (Button, Card, Table, DataTable, PageShell, NavMain, …) — the plugin SDK surface, tracked in etc/ui-components.api.md. | | @oc-mui/ui/components/icons | lucide-react icons re-exported with a stable surface (Home, Video, ExternalLink, …). | | @oc-mui/ui/lib | Utility helpers (resolveFirstAssetUrl, …). | | @oc-mui/ui/lib/utils | The cn() class-merging helper. | | @oc-mui/ui/hooks | useIsMobile, useClickOutside. | | @oc-mui/ui/internal | Host-only assembly layer: Appshell, the router primitives (UiRouterProvider), DefaultLandingPage, the error pages, ThemeModeProvider. Not part of the SDK, no API report, not shared with remote plugins, lint-forbidden inside plugins/. | | @oc-mui/ui/styles, @oc-mui/ui/globals.css | The semantic-token CSS. Imported once by the shell. | | @oc-mui/ui/config-primitives | Building blocks for plugin config UIs. | | @oc-mui/ui/postcss.config | Deprecated, no-op. Tailwind runs through @tailwindcss/vite (wired by @oc-mui/vite-config); a host needs no PostCSS config. Kept as an empty config for one major cycle. |

Components

The library is split between atomic shadcn components (under src/components/ui/) and composed components (everything else under src/components/). The atomic ones are generated by npx shadcn@latest add; the composed ones are hand-written and depend on them.

| Composed component | What it does | |--------------------|--------------| | AppShell | The shell's layout — sidebar, header, footer, main content area. The host mounts this once; plugin extension points fill the slots. | | DataTable / MuiTable | Sortable, filterable, paginated tables — the canonical way to render lists. | | MetadataField, MetadataUpdateField | Form controls for Opencast metadata. | | AclEditor | Access-control-list editor. | | DatePicker, DateTimePicker | Calendar input. | | InfiniteScroll | Sentinel-driven incremental loading. | | SortableList | Vertically sortable list with a drag handle, full keyboard reordering, and screen-reader announcements; moveItem for non-drag moves. | | Container, AppHeading, OverflowTooltip, DebouncedInput | General-purpose layout/UX. |

Theme

Components consume the semantic tokens from src/styles/globals.css. Org themes override the token values, not the class names. Full contract: docs/extend/styling.md.

PageShell — the standard page frame

Content pages (episodes, series, upload, marketplace) render inside PageShell: uniform page padding, the title in the same place and type scale everywhere, optional description, an optional right-aligned actions slot, separator, then the content. Plugin apps should use it too, so their pages sit visually flush with the core ones. The landing page deliberately does not — it is a marketing surface, not a content page.

Layer

Integration. Depends on @oc-mui/i18n, @oc-mui/plugin-system, @oc-mui/query, @oc-mui/ui-config, @oc-mui/utils.

Deliberately not a dependency: @oc-mui/router. Router-aware components (sidebar nav, data table) get their Link/usePathname primitives injected by the host via UiRouterProvider — importing the router here would invert the layering and create a dependency cycle. See src/components/router-context.tsx for the full rationale.

See also