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

@auspices/eos

v6.1.0

Published

A React UI library

Readme

@auspices/eos

A React UI library

semantic-release npm CircleCI

Meta

  • State: production

Design Goals

Eos is designed for use in situations where it is desirable to minimize visual hierarchy. This results in the creation of user interfaces that rely on thoughtful composition for differentiation, rather than on the stylistic differences between components.

Usage

Next.js App Router

  • Use @auspices/eos/client for UI components (including when rendered from Server Components).
  • Use @auspices/eos/server for server-safe utilities and theme tokens.
// app/page.tsx (Server Component)
import { THEME } from "@auspices/eos/server";
import { Tag } from "@auspices/eos/client";
"use client";

import { Dropdown, Modal, useConfirm } from "@auspices/eos/client";

Theme Imports

  • Import theme primitives from @auspices/eos/theme.

Using eos with next-themes (controlled mode)

When your app theme is managed by next-themes, pass the resolved light | dark scheme directly into ThemerProvider. This keeps eos and your app on the same authoritative theme source and avoids mixed first paint.

// pages/_app.tsx
import type { AppProps } from "next/app";
import React, { useEffect, useMemo, useState } from "react";
import { ThemeProvider as NextThemesProvider, useTheme } from "next-themes";
import { ThemeProvider as StyledThemeProvider } from "styled-components";
import { GlobalStyles, ThemerProvider, useThemer } from "@auspices/eos/client";
import type { Scheme } from "@auspices/eos/theme";

const getSchemeFromDom = (): Scheme => {
  if (typeof document === "undefined") return "light";
  const fromAttribute = document.documentElement.getAttribute("data-theme");
  return fromAttribute === "dark" ? "dark" : "light";
};

const EosThemeBridge: React.FC<{ children: React.ReactNode }> = ({ children }) => {
  const { resolvedTheme, setTheme } = useTheme();
  const [mounted, setMounted] = useState(false);
  const [fallbackScheme] = useState<Scheme>(getSchemeFromDom);

  useEffect(() => {
    setMounted(true);
  }, []);

  const scheme = useMemo<Scheme>(() => {
    if (resolvedTheme === "dark" || resolvedTheme === "light") return resolvedTheme;
    return fallbackScheme;
  }, [fallbackScheme, resolvedTheme]);

  if (!mounted) return null;

  return (
    <ThemerProvider scheme={scheme} setScheme={(nextScheme) => setTheme(nextScheme)}>
      <EosStyledThemeProvider>{children}</EosStyledThemeProvider>
    </ThemerProvider>
  );
};

const EosStyledThemeProvider: React.FC<{ children: React.ReactNode }> = ({ children }) => {
  const { theme } = useThemer();
  return (
    <StyledThemeProvider theme={theme}>
      <GlobalStyles />
      {children}
    </StyledThemeProvider>
  );
};

export default function App({ Component, pageProps }: AppProps) {
  return (
    <NextThemesProvider attribute="data-theme" defaultTheme="system" enableSystem>
      <EosThemeBridge>
        <Component {...pageProps} />
      </EosThemeBridge>
    </NextThemesProvider>
  );
}
// pages/_document.tsx
import Document, { Html, Head, Main, NextScript } from "next/document";

export default class MyDocument extends Document {
  render() {
    return (
      <Html suppressHydrationWarning>
        <Head />
        <body>
          <Main />
          <NextScript />
        </body>
      </Html>
    );
  }
}

Notes:

  • In controlled mode, eos does not read or write local storage for scheme state.
  • next-themes remains the only source of truth.
  • Ensure the scheme prop is always a concrete light or dark value.
  • Avoid rendering useTheme()-derived UI until client mount to prevent hydration mismatch.
  • See examples/next-pages-next-themes for a complete pages-router SSR integration.

Local Example App

yarn install
yarn workspace eos-next-minimal dev
yarn workspace eos-next-pages-next-themes dev

For production validation:

yarn verify:release