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

@k8ordo/static

v0.1.0

Published

Builds a k8ordo application into files: every route rendered ahead of time, no server at run time.

Downloads

18

Readme

@k8ordo/static

Builds a k8ordo application into files. Every route is rendered ahead of time — React Server Components at build time — and what ships is a directory a static host can serve: HTML per page, its RSC payload beside it for client navigation, 404.html, and a sitemap. No server at run time.

Like every k8ordo package it assumes React 19 and Server Components, uses only what has reached Baseline newly available, and ships no polyfills or legacy fallbacks.

  • Documentation: https://ordo.k8o.me/static
  • Design guide: docs/GUIDE.md — shipped inside this package

Installation

pnpm add @k8ordo/router react react-dom server-only
pnpm add -D @k8ordo/static vite

The mode is the dependency: installing this package is what makes the application static, and @k8ordo/server is the other choice. Nothing else about the application changes between them.

Peer Dependencies

| Package | Version | Needed for | | ---------------- | ------- | ------------------------------------------ | | @k8ordo/router | ^0.1.0 | the route table the framework generates | | react | ≥19.2.6 | rendering | | react-dom | ≥19.2.6 | rendering | | vite | ≥8.2.1 | the build (framework() is a Vite plugin) |

Quick Start

// vite.config.ts
import { framework } from '@k8ordo/static';
import { defineConfig } from 'vite';

export default defineConfig({
  plugins: [
    framework({
      paths: () => ['/products/1', '/products/2'], // for routes with parameters
      site: 'https://example.com', // and a sitemap.xml
    }),
  ],
});
src/routes/
  layout.tsx            <html> and <body>; wraps everything through `children`
  page.tsx              /
  not-found.tsx         404.html
  error.tsx             shown in place of what is below when it throws
  products/[id]/page.tsx   /products/:id — `export const paramsSchema` types :id
  old/redirect.ts       /old sends the visitor elsewhere
vite dev     # a real server, so the pages behave as they will in production
vite build   # dist/client/ is the site

Server is the default; the browser side is opted into with 'use client', and a module that imports server-only can never reach the client bundle. A 'use server' module fails the build — and vite dev — by name: a file cannot receive a Server Action, and that application wants @k8ordo/server.

AI Agent Documentation

The docs ship inside the package, so an agent always reads the exact version you installed — there is no snapshot to copy or re-sync on upgrade.

Point your agent at them once by pasting this into your project's CLAUDE.md / AGENTS.md:

This application is built with `@k8ordo/static`. Before adding or changing a
route, read `node_modules/@k8ordo/static/docs/GUIDE.md`. `src/routes/` is
the pathname space and holds only page.tsx, layout.tsx, not-found.tsx,
error.tsx and redirect.ts; everything else goes under a `_`-prefixed
directory. Never edit `.k8ordo/` — it is generated. Build links with
`href()` from `@k8ordo/router`; search params are `@k8ordo/state`'s.

What each surface gives an agent:

| Surface | Where | | -------------------------- | ---------------------------------------------- | | Design guide (entry point) | node_modules/@k8ordo/static/docs/GUIDE.md | | Docs index for LLMs | docs/llms.txt · https://ordo.k8o.me/llms.txt | | Markdown twin on the web | https://ordo.k8o.me/static/docs/GUIDE.md |

License

MIT License - see LICENSE for details.