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

@coderlifenet/ui-core

v0.1.0-alpha.2

Published

Compatibility facade over Material UI with optional instrumentation runtime.

Readme

@coderlifenet/ui-core

@coderlifenet/ui-core is a compatibility facade over Material UI with deterministic export generation plus an opt-in extension runtime for instrumentation.

Baseline

  • React: 19.2.8
  • React DOM: 19.2.8
  • TypeScript: 7.0.2
  • Material UI: 9.4.0
  • Styling engine: @emotion/react 11.14.0, @emotion/styled 11.14.1

Installation

pnpm add @coderlifenet/[email protected] @mui/[email protected] @emotion/[email protected] @emotion/[email protected] [email protected] [email protected]

Optional coverage:

pnpm add @mui/lab @mui/icons-material

Compatibility Imports

Root import parity:

import { Button, TextField } from "@coderlifenet/ui-core";

Per-component parity:

import Button from "@coderlifenet/ui-core/Button";

Optional entry points:

import { Timeline } from "@coderlifenet/ui-core/lab";
import { Home } from "@coderlifenet/ui-core/icons";

Extensions Runtime

import { UIExtensionsProvider, TrackingBoundary, useUIExtensions } from "@coderlifenet/ui-core/extensions";
import { createAnalyticsRuntime } from "@coderlifenet/ui-core/analytics";
import { createMemoryAdapter } from "@coderlifenet/ui-core/analytics";
import { createAnalyticsExtension } from "@coderlifenet/ui-core/extensions";

const memory = createMemoryAdapter();
const analyticsRuntime = createAnalyticsRuntime([memory], {
  enabled: true,
  consent: { analyticsStorage: "granted", adStorage: "denied" }
});
memory.configure?.({ enabled: true, sampleRate: 1 });

<UIExtensionsProvider
  initialConfig={{ enabled: true }}
  extensions={[createAnalyticsExtension(analyticsRuntime)]}
>
  <TrackingBoundary id="app-shell">{/* app */}</TrackingBoundary>
</UIExtensionsProvider>;

Analytics Defaults

  • Global analytics delivery is disabled by default.
  • Consent must be explicitly granted (analyticsStorage: "granted").
  • No vendor SDK script is loaded by this package.
  • Host applications own SDK loading, lifecycle, and consent wiring.

Inventory and Drift

  • Generated stable surface inventory: generated/mui-surface.json
  • Generated export map: generated/mui-export-map.json

Commands:

pnpm generate
pnpm check:generated
pnpm typecheck
pnpm test
pnpm build

Explicit Exclusions

  • MUI X packages are inventoried as out-of-scope for parity claims.
  • Private/internal MUI paths are intentionally excluded.
  • Documentation-only recipes are documented but not exported as runtime APIs.