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

@locusgraph/marketing

v0.1.0

Published

Landing page sections built from @locusgraph/components: navbar, hero, features, logos, testimonials, pricing, FAQ, call to action, waitlist and footer, with content as props.

Readme

@locusgraph/marketing

npm MIT license

Docs · Source · All packages

Landing page sections built from @locusgraph/components. Every block takes its content as props, so a template passes data instead of editing markup. Blocks are server components; only the interactive parts (the navbar's mobile menu, the pricing toggle and the waitlist form) are client components, so a page stays server rendered in the Next.js App Router.

It is a separate package from @locusgraph/blocks so product apps never scan or ship marketing styles, and marketing releases never bump the blocks that apps and @locusgraph/json-render depend on.

pnpm add @locusgraph/marketing @locusgraph/components
@import "@locusgraph/components/theme.css";
@import "@locusgraph/marketing/sources.css";

| Block | Props | |---|---| | Navbar | logo, logoHref, links, actions, end (such as a theme toggle), menuLabel, sticky, linkComponent. Links and actions move into a sheet below the md breakpoint | | Hero | title (the page h1), description, eyebrow, actions, media (screenshot, video or illustration), layout (centered or split), linkComponent | | Features | items ({ title, description?, icon? }[]) in a ruled grid, columns (2, 3 or 4) | | FeatureRows | rows ({ eyebrow?, title, description?, media, actions? }[]): text beside media, switching sides every row on large screens | | LogoCloud | logos ({ name, logo, href? }[]). Each logo is named for screen readers and links when it has an href | | Testimonials | testimonials ({ quote, name, role?, avatar? }[]). One is featured large; two or more sit in a ruled grid | | Pricing | plans ({ name, description?, price, priceNote?, features?, action, highlighted?, badge? }[]), defaultPeriod, periodLabels, cadence. A plan's price is a string or { monthly, yearly }; with any of the second, a toggle switches every plan. Both prices render on the server | | Faq | items ({ question, answer }[]) on the Accordion | | CtaBand | title, description, actions on a full-width tinted band | | Waitlist | A section around WaitlistForm: onSubmit(email) returns nothing on success or { error }; a throw shows errorText. Also buttonLabel, placeholder, successText, note. In Next.js, pass a server action | | Footer | logo, tagline, columns ({ title, links }[]), legal, copyright, end, linkComponent | | Section, SectionHeading | The frame every section uses: eyebrow, title (an h2), description, align, id. Use them for your own sections | | MarketingActions | actions, size, linkComponent. The buttons the blocks use: the first action is primary, the rest outline, unless an action sets variant |

Every section takes eyebrow, title, description, align and id (for navbar anchors). Links are { label, href }; actions add an optional variant (default, outline or ghost). Pass your router's link as linkComponent (next/link in Next.js).

import { Footer, Hero, Navbar } from "@locusgraph/marketing";
import Link from "next/link";

export default function Home() {
  return (
    <>
      <Navbar
        logo={<Logo />}
        links={[{ label: "Pricing", href: "/pricing" }]}
        actions={[{ label: "Start free", href: "/signup" }]}
        linkComponent={Link}
      />
      <Hero
        layout="split"
        title="Every agent run, priced"
        description="See what each run costs before you approve it."
        actions={[{ label: "Start free", href: "/signup" }]}
        media={<Screenshot />}
        linkComponent={Link}
      />
      <Footer copyright="© 2026 Acme" legal={[{ label: "Privacy", href: "/privacy" }]} />
    </>
  );
}

Blocks use the theme's tokens only, so they follow any theme set with the shadcn variables (see @locusgraph/tokens).