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

@sveltebuilder/content

v0.0.5

Published

Publisher/news domain module for SvelteBuilder — articles, sections, taxonomy, live coverage, newsletters, comments, RSS, sitemaps, and JSON-LD, with a Drizzle schema and i18n built in.

Readme

@sveltebuilder/content

Publisher/news domain module for SvelteBuilder: articles, editorial sections, taxonomy, live coverage, newsletters, and comments — with RSS, sitemaps, and JSON-LD structured data included.

Install

npm install @sveltebuilder/content @sveltebuilder/hermes @sveltebuilder/coreui

Typically installed via npm create sveltebuilder@latest, which also copies the module's schema and starter routes into your project. Installing it directly gives you the components, server helpers, and Drizzle schema as a standalone library.

Usage

import { ArticleCard, ArticleView, SectionFront } from '@sveltebuilder/content';
import { getPublishedArticles, getPublishedArticleBySlug } from '@sveltebuilder/content/server';
import { article, section, comment } from '@sveltebuilder/content/schema';
  • @sveltebuilder/content — Svelte components, split into Camp 1 (ArticleList, AssignmentQueue, BlockEditorHost, FrontCurationBoard, SubscriberList — no hermes dependency) and Camp 2 (ArticleCard, ArticleView, ArticleWorkflowPanel, AuthorProfileView, SectionFront, NewsletterSignup, and more — import hermes and require hermes.load() before mount). Also re-exports all schema types.
  • @sveltebuilder/content/server — query helpers (getPublishedArticles, createArticle, transitionArticleStatus, subscribeToNewsletter, …), feed generation (generateRssFeed), sitemaps (generateStandardSitemap, generateNewsSitemap), and structured data (buildNewsArticleJsonLd, buildArticleMetaTags, buildHreflangAlternates).
  • @sveltebuilder/content/schema — Drizzle table definitions and TypeScript types (Article, Section, Comment, Newsletter, MediaAsset, Front, LiveCoverage, and more).

Like all SvelteBuilder domain modules, content carries no name/title/body copy columns on its entities — user-facing copy is linked via @sveltebuilder/hermes (scope = table name, entityId = the row's bigint PK). Two documented exceptions carry literal data instead of copy: comment.author_name/author_email/body (reader-submitted, not editorial) and subscriber.email_address (PII).

Part of the SvelteBuilder ecosystem

See the SvelteBuilder README for the full architecture, including how domain modules relate to @sveltebuilder/hermes, @sveltebuilder/coreui, and the CLI sync workflow.