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

@nexub/marketing

v10.0.0

Published

Marketing sections for the Nexub Design System: hero, stats, testimonials, products, pricing, FAQ, CTA, nav and footer, built on @nexub/react in marketing mode. Server components by default.

Readme

@nexub/marketing

Marketing sections for the Nexub Design System, built only from @nexub/react and the design tokens: the building blocks of nexub.com.

pnpm add @nexub/marketing @nexub/react @nexub/patterns @nexub/icons @nexub/themes @nexub/tokens

| Section | Renders on | |---|---| | Hero, SectionHeader, LogoStrip, StatBand + StatBandItem, TestimonialGrid + TestimonialCard, ProductGrid + ProductCard, HowItWorks, FeatureSplit, CTABand, MarketingFooter | the server (React Server Components) | | MarketingNav, PricingTable, FAQ | the client ('use client') |

StatBandItem is named apart from @nexub/patterns' StatCard, so both packages can be used together.

Marketing mode

The sections take their look from marketing mode: set data-mode="marketing" on <html> (or any wrapper) and load @nexub/themes/marketing. Nothing outside that attribute changes, so an app and its marketing pages can share one stylesheet.

Next.js (App Router) with Tailwind 4

/* app/globals.css */
@import "tailwindcss";
@import "@nexub/tokens/tailwind.css";
@import "@nexub/themes/core" layer(base);   /* resets, no fonts, no page backdrop */
@import "@nexub/themes/light" layer(base);
@import "@nexub/themes/dark" layer(base);
@import "@nexub/themes/marketing" layer(base);
@source "../node_modules/@nexub/react/dist";
@source "../node_modules/@nexub/patterns/dist";
@source "../node_modules/@nexub/marketing/dist";

Don't also import @nexub/react/styles.css: it's the prebuilt CSS for apps without Tailwind and brings a second preflight.

Fonts come from next/font; point the design tokens at them:

// app/layout.tsx
import { Inter, Plus_Jakarta_Sans } from 'next/font/google';
const sans = Inter({ subsets: ['latin'], variable: '--font-family-sans' });
const display = Plus_Jakarta_Sans({ subsets: ['latin'], variable: '--font-family-display' });

export default function RootLayout({ children }: { children: React.ReactNode }) {
  return (
    <html lang="en" data-mode="marketing" className={`${sans.variable} ${display.variable}`}>
      <body>{children}</body>
    </html>
  );
}
// app/page.tsx: a server component
import { Button } from '@nexub/react';
import { CTABand, Hero, StatBand, StatBandItem } from '@nexub/marketing';

export default function Page() {
  return (
    <main>
      <Hero
        eyebrow="Now in Vietnam"
        title="Run your whole company in one place"
        description="Payroll, bookkeeping and compliance for growing teams."
        actions={<><Button variant="hero" size="lg" asChild><a href="/start">Start free</a></Button><Button variant="outlined" size="lg" asChild><a href="/demo">Book a demo</a></Button></>}
      />
      <StatBand>
        <StatBandItem value={2000} suffix="+" label="Teams" />
        <StatBandItem value={5} label="Countries" tone="success" />
      </StatBand>
      <CTABand title="Start today" actions={<Button variant="filled" tone="neutral" asChild><a href="/start">Create an account</a></Button>} />
    </main>
  );
}

Each section is also importable on its own, e.g. @nexub/marketing/Hero.

Guidelines: gradients only on the hero, the main button and the CTA band; at most one glowing (variant="hero") button per screen; product accents only on product-specific content. See the Marketing mode page in the docs.