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

@web4kit/next

v0.3.0

Published

web4 for Next.js: one call from a server component plans, resolves and previews a page per visitor.

Readme

@web4kit/next

web4 for Next.js (App Router). One call from a server component resolves the visitor's context, derives the situation, plans the page (one System One round or a plan-cache hit), and fetches the data with the planned situation. Development-only persona previews come built in.

Part of web4: pages planned per visitor by System One decision models.

Experimental (0.x): APIs may change between minor versions.

Install

pnpm add @web4kit/next

Usage

// web4/site.ts (server only)
import { createSite } from "@web4kit/next";

export const site = createSite({
  manifests,
  situation: RULES,           // SituationRule[] or (envelope) => situation
  decider,                    // optional: rules when omitted
  calibration,                // optional profile
  personas: PERSONAS,         // ?as=<name> previews, development only
  enrich: async (env, req) => env, // first-party facts for real requests
});
// app/page.tsx
import { PreviewBar } from "@web4kit/next";
import { defaultRegistry, PlanView } from "@web4kit/react";
import { site } from "@/web4/site";

export const dynamic = "force-dynamic";

export default async function Home({ searchParams }: { searchParams: Promise<Record<string, string>> }) {
  const page = await site.page({ searchParams });
  return (
    <>
      <PreviewBar site={site} page={page} statsHref="/stats" />
      <PlanView plan={page.plan} data={page.data} manifests={site.manifests} registry={defaultRegistry} />
    </>
  );
}

PreviewBar renders only when previews are on. Besides the persona links, it shows a notice when the page was planned by the rules engine alone (no decider configured) or by an engine whose calibration profile is missing or stale, since every answer then falls back to rules.

site.handle({ url, headers }) is the framework-agnostic entry, and site.stats() returns the planner's counters (pages, cache hits, tokens, cost, calibration status).

Order of operations: persona preview (only when previews are on; off in production by default) → context → enrich (real requests only) → situation → plan → data.

License

MIT