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

@grove-dev/astro

v1.1.0

Published

Astro integration + server view-models for Grove directories. UI ships from @grove-dev/registry, not from this package.

Readme

@grove-dev/astro

Astro integration, generated-data adapters, server view-model helpers, and the composable UI used by Grove-powered sites.

The integration prepares generated data before Astro runs, aliases the source directories of the package's components and layouts so consumers can write import ProjectCard from "@grove-dev/astro/components/ProjectCard.astro", auto-loads the consumer's src/styles/global.css when it exists, and re-exports the framework-agnostic helpers from @grove-dev/core.

It does not inject routes. Every route lives in the consumer's src/pages/, where it can be reordered, replaced, or extended without a Grove sync overwriting it.

Install

pnpm add @grove-dev/astro

Requires Node.js >=22.12.0 and Astro ^6.0.0 || ^7.0.0.

Enable the integration

// astro.config.mjs
import { defineConfig } from "astro/config";
import grove from "@grove-dev/astro";

export default defineConfig({ integrations: [grove()] });

When grove() loads it:

  1. Runs prepareDirectory() so @grove/generated is up to date before astro dev, astro check, or astro build.
  2. Loads grove.config.ts and syncs the packaged icons into the consumer's public/icons/.
  3. Aliases @grove-dev/astro/components, @grove-dev/astro/layouts, and @grove/generated to their on-disk locations.
  4. Injects the consumer's src/styles/global.css when present, so brand tokens defined there take effect without manual imports.

What this package ships

| Surface | Contents | | --- | --- | | @grove-dev/astro | The integration plus re-exports of @grove-dev/core and the generic lib/ helpers (search, lenses, scores, repo, format, display, taxonomy counts). | | @grove-dev/astro/components | Composable .astro components — Hero, Card, Icon, FilterGroupMenu, SearchField, ThemeToggle, MarkdownBody, and more. | | @grove-dev/astro/layouts | Page-level layouts — BaseLayout, Container, Header, Footer, SectionHeader, Seo. | | @grove-dev/astro/server | View-model helpers that take generated data and return the props a page expects. | | @grove-dev/astro/ui | Small UI primitives — Button, Badge, EmptyState, FilterDrawer, PageHeader. | | @grove-dev/astro/styles.css | The shared Grove stylesheet imported from the consumer's global layout. |

Server view models

@grove-dev/astro/server builds the props each page needs from the generated data, so route files stay small and pages remain declarative.

// src/pages/index.astro
import { BaseLayout, Hero, Card } from "@grove-dev/astro";
import { buildHomeModel } from "@grove-dev/astro/server";

const model = await buildHomeModel();
---
<BaseLayout seo={model.seo}>
  <Hero {...model.hero} />
  <Card {...model.featuredCard} />
</BaseLayout>

Routes stay in the consumer project

grove init copies a complete working set of home, list, record detail, about, contributors, submit, 404, and legacy redirect pages from the canonical apps/example/ scaffold. The copy is the source of truth for those routes — the integration never injects them.

To customize a page, edit the file in src/pages/ directly. Grove will not overwrite it on the next sync.

Develop Astro

pnpm --filter @grove-dev/astro check
pnpm --dir apps/example build

License

MIT © Grove contributors.