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

oceanic-ui

v0.0.5

Published

<p align="center"> <img src=".github/assets/logo.png" alt="oceanic-ui" width="112"> </p>

Readme

[!NOTE] Pre-1.0. The API is still settling — expect breaking changes between minor versions until 1.0.0.


The look: a desktop toolkit, on the web

Ocean shipped as the default cross-platform Java look and feel in 2004. oceanic-ui borrows its grammar, not a pixel-for-pixel clone:

  • Cool, near-white gradients — controls fade from almost-white to a pale blue, never a saturated fill.
  • Raised vs. recessed surfaces — buttons lift toward you, form fields sink in. Your eye tells "click here" from "type here" before reading a word.
  • Restrained rounding — 3–10px corners. A rounded rectangle reads as a real control; a full pill reads as a 2010 mobile app.
  • Glow, not gloss — the only shine is a soft blue ring on :focus-visible. No reflections, no sweeps, nothing sitting on top of a control.
  • Every surface opaque — no frosted glass, no backdrop-filter.

The full rationale lives in docs/design-language.md.

Add it to your project

npm install oceanic-ui

react / react-dom 19 and tailwindcss 4 are peer dependencies.

Your first component

import { Button, Card, Text } from 'oceanic-ui'
import 'oceanic-ui/styles.css'

export function Example() {
  return (
    <Card>
      <Text variant="headingSmall" as="h2">
        Ready when you are
      </Text>
      <Button onClick={() => console.log('clicked')}>Get started</Button>
    </Card>
  )
}

Every component ships with full TypeScript types and forwards its ref.

Loading the stylesheet

oceanic-ui/styles.css is precompiled — every class the components use is already real CSS, so nothing has to scan node_modules and there's no Tailwind config to write. Import it once, whichever way suits your setup:

// …in your JS entry point
import 'oceanic-ui/styles.css'
/* …or at the top of your global stylesheet */
@import 'oceanic-ui/styles.css';

Bring your own CSS reset / preflight — the stylesheet deliberately ships without one.

Restyling: plain Tailwind classes win

Every component is built from Tailwind v4 utilities composed with cva. Pass a className and conflicting utilities replace the component's own deterministically — a configured tailwind-merge resolves the conflict instead of letting both fight in the cascade:

// the component's height/padding lose cleanly to yours
<Button className="h-12 px-8">Bigger</Button>

If you use Tailwind in your app, add it above the library import so your utilities land in the same layers:

@import 'tailwindcss';
@import 'oceanic-ui/styles.css';

See docs/css-architecture.md for how the layering is wired.

What's in the box

43 components today. docs/roadmap.md tracks what's built and what's next (Table, DatePicker…).

| Group | Components | |---|---| | Actions & navigation | Button · IconButton · SegmentedControl · Pagination · Breadcrumb · Menu · Sidebar | | Forms & inputs | Input · Textarea · Select · Checkbox · Radio · Switch · Slider · FileUpload · Composer | | Feedback & status | Dialog · Popover · Tooltip · Toast · Alert · Progress · Spinner · Skeleton · Badge | | Chat & agent | Composer · Message · Bubble · Attachment · Empty · Marker · IconSwap · Pulse · Thinking · ToolCall | | Layout & display | Card · Divider · List · Accordion · Tabs · Avatar · CodeBlock | | Primitives | Text · Icon |

Browse every one — with live controls — at oceanic-ui.netlify.app, or run Storybook locally (below).

Working on the library

git clone https://github.com/rjamador/oceanic-ui.git
cd oceanic-ui
npm install

| Command | What it does | |---|---| | npm run dev | The local demo app (src/App.tsx) | | npm run storybook | Every component in isolation, with controls | | npm test | Vitest + Testing Library | | npm run lint | ESLint | | npm run build:lib | The publishable build — ESM, .d.ts, and dist/styles.css | | npm run build:site | Build the marketing site in site/ |

Before you send a PR

Read these first — they're short:

License

MIT © Roberto Amador