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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@oef/components

v1.1.0

Published

CityCatalyst UI components including typography and buttons packaged from app/src/components/package

Readme

@oef/components

A TypeScript package containing text/typography components and module components from CityCatalyst. This package provides consistent UI components built on top of Chakra UI.

Installation

npm install @oef/components

Peer Dependencies

This package requires the following peer dependencies:

npm install react react-dom @chakra-ui/react @emotion/react i18next

Usage

import { 
  BlueSubtitle, 
  BodyLarge, 
  DisplayMedium, 
  HeadlineSmall,
  TitleLarge,
  GHGIDashboard,
  HIAPDashboard,
  CCRADashboard
} from '@oef/components';

function MyComponent() {
  return (
    <div>
      <DisplayMedium>Main Heading</DisplayMedium>
      <HeadlineSmall>Section Title</HeadlineSmall>
      <BodyLarge>This is some body text content.</BodyLarge>
      <BlueSubtitle t={t} text="subtitle.key" />
      
      {/* Module Components */}
      <GHGIDashboard />
      <HIAPDashboard />
      <CCRADashboard />
    </div>
  );
}

Available Components

Display Components

  • DisplaySmall - Small display text
  • DisplayMedium - Medium display text
  • DisplayLarge - Large display text

Headline Components

  • HeadlineSmall - Small headline
  • HeadlineMedium - Medium headline
  • HeadlineLarge - Large headline

Title Components

  • TitleSmall - Small title
  • TitleMedium - Medium title
  • TitleLarge - Large title

Body Text Components

  • BodySmall - Small body text
  • BodyMedium - Medium body text
  • BodyLarge - Large body text
  • BodyXLarge - Extra large body text

Label Components

  • LabelMedium - Medium label
  • LabelLarge - Large label

Button Text Components

  • ButtonSmall - Small button text
  • ButtonMedium - Medium button text

Special Components

  • BlueSubtitle - Blue colored subtitle with i18n support
  • Overline - Overline text component

Module Components

  • GHGIDashboard
  • HIAPDashboard
  • CCRADashboard

Development

This package references the original components in the main CityCatalyst app, so you can continue editing them in their original location at app/src/components/Texts/ and app/src/components/Modules/. Changes will be automatically reflected when the package is rebuilt.

Building the Package

npm run build

Cleaning Build Artifacts

npm run clean

License

LGPL

Using the package locally (without publishing)

Option A: npm pack (recommended)

Create a tarball from the package and install it in the consumer:

# From the package folder
cd CityCatalyst/app/src/components
npm run build
npm pack            # → produces something like oef-components-1.0.4.tgz

# In the consuming app
cd ../../../demo-oef-components
npm install ../CityCatalyst/app/src/components/@oef/components-*.tgz

This mimics a real npm install (no nested node_modules in the package), and is closest to what you'll publish.

Option B: file: path

cd demo-oef-components
npm pkg set dependencies.@oef/components="file:../CityCatalyst/app/src/components"
npm install

Publishing to npm

  1. Log in with an account belonging to the oef organization.
npm login
  1. Ensure a clean build and bump version:
cd CityCatalyst/app/src/components
npm ci
npm run clean && npm run build
npm version minor   # or minor/major
  1. Publish (requires npm account with access):
npm publish --access public

Notes:

  • This package ships compiled JS and type declarations from dist/.
  • Verify name and version in package.json before publishing.

Next.js + Chakra setup (in consumer)

Wrap your app with Chakra’s provider and pass a theme value:

// app/providers.tsx
"use client";
import { ReactNode } from 'react';
import { ChakraProvider, createSystem, defaultConfig } from '@chakra-ui/react';
const appTheme = createSystem(defaultConfig, {});
export function Providers({ children }: { children: ReactNode }) {
  return <ChakraProvider value={appTheme}>{children}</ChakraProvider>;
}