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

@kuloudx/mobius-ui

v1.1.0

Published

Business-neutral React UI components, semantic themes and desktop/mobile templates

Vulnerabilities

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

Links

Git

Maintainers

kuloudxkuloudx

Keywords

Readme

Mobius UI

Version 1.1.0 release prepared; registry publication pending, npm stable 1.0.0. Business-neutral React components and desktop/mobile templates, with an optional native Taro adapter.

npm install @kuloudx/mobius-ui react react-dom radix-ui
import { ThemeProvider, Button, Panel } from '@kuloudx/mobius-ui';
import '@kuloudx/mobius-ui/styles.css';

<ThemeProvider theme="indigo" mode="light" density="comfortable">
  <Panel title="Workspace">
    <Button onClick={save}>Save</Button>
  </Panel>
</ThemeProvider>;

Themes: evergreen, indigo, graphite. Modes: light/dark. Density: comfortable/touch. Mobile browser templates use density="touch".

Native Taro 4.2

import { Theme, Panel, Button } from '@kuloudx/mobius-ui/taro';
import '@kuloudx/mobius-ui/taro/tokens.css';
import '@kuloudx/mobius-ui/taro/components.css';

Install @tarojs/taro and @tarojs/components only for this entry. Do not import the Web entry or Radix into a mini-program. Native adapter currently includes Theme, Button, Panel, Field, Badge, EmptyState, CopyText, Thumbnail and BottomSheet; it does not promise parity for every desktop template.

Application contracts

Data, authorization, navigation, uploads, revision conflicts, idempotency and writes remain in the application. Components never fake saved or approved state. Field associates a single direct control automatically; compound/custom containers require explicit id, aria-invalid and aria-describedby. Dialog consumers own dirty-draft close policy. CopyText requires clipboard access in a secure browser context.

See DESIGN-SYSTEM.md for tokens, states, composition, accessibility targets and verification limits. See CHANGELOG.md for version changes. Public demos are excluded from the npm package.

Maintenance and consumption

Mobius is maintained as an independent project. It owns the npm package, tokens, Storybook, tests and release records. Consumer applications (including Agrova) install a reviewed exact npm version; they must not import sibling repository paths, link workspace sources in production or copy universal component implementations. Application adapters may map existing brand tokens and retain application APIs/permissions. Web and native Taro are migrated and verified separately.

Run pnpm storybook in the Mobius repository for live component development and pnpm check before release. Package changes follow SemVer; consumers upgrade deliberately after regression checks. See the workbench's contribution guide for state and accessibility requirements.