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

@unterberg/nivel

v0.1.5

Published

Opinionated docs engine for Vike + Vite + React.

Readme

@unterberg/nivel

Opinionated docs engine for Vike + Vite + React.

@unterberg/nivel owns the docs runtime: Vike integration, MDX setup, docs-graph validation, route code generation, page shell rendering, and reusable docs UI primitives. The consumer stays thin and keeps its content, docs graph, visible Vike shell files, and theme files local.

What It Provides

  • typed docs config and docs graph helpers
  • generated Vike docs pages from a single docs graph
  • docs shell primitives such as navbar, sidebar, table of contents, pagination, search, and meta head wiring
  • MDX support with built-in docs components and code-block tooling
  • Tailwind v4 and daisyUI integration helpers
  • a small CLI for consumer scaffolding and docs page generation

Install

pnpm add @unterberg/nivel react react-dom vike vike-react
pnpm add -D vite typescript @types/react @types/react-dom

vike and vite are peer dependencies. The package exposes a local nivel binary after install.

Quick Start

Scaffold a consumer:

pnpm exec nivel init

Generate docs pages:

pnpm exec nivel prepare

Typical consumer scripts:

{
  "scripts": {
    "generate:docs": "nivel prepare",
    "predev": "pnpm generate:docs",
    "dev": "vike dev",
    "prebuild": "pnpm generate:docs",
    "build": "vike build",
    "pretypecheck": "pnpm generate:docs",
    "typecheck": "tsc --noEmit -p tsconfig.json"
  }
}

Consumer Shape

Keep these files local and visible in the consumer:

  • docs/docs.graph.ts
  • pages/+docs.ts
  • pages/+config.ts
  • pages/+Head.tsx
  • pages/+Layout.tsx
  • pages/+onCreateGlobalContext.ts
  • pages/+Wrapper.tsx
  • global.d.ts
  • docs content, brand assets, and consumer CSS/theme files

Only pages/(nivel-generated) is engine-generated and should not be edited by hand.

docs/docs.graph.ts is the single source of truth for docs structure. Navbar and sidebar behavior come from that graph.

Minimal Setup

docs/docs.graph.ts

import { defineDocsGraph } from '@unterberg/nivel/config'

export const docsGraph = defineDocsGraph({
  items: [
    {
      kind: 'section',
      id: 'docs',
      title: 'Docs',
      items: [
        {
          kind: 'page',
          id: 'gettingStarted',
          title: 'Getting Started',
          slug: 'getting-started',
          source: 'content/getting-started/content.mdx',
          description: 'Getting started with @unterberg/nivel.',
        },
      ],
    },
  ],
})

pages/+docs.ts

import { defineDocsConfig } from '@unterberg/nivel/config'
import { docsGraph } from '../docs/docs.graph'

const docsConfig = defineDocsConfig({
  graph: docsGraph,
  siteTitle: 'My Docs',
  siteDescription: 'Documentation site powered by @unterberg/nivel.',
  basePath: '/docs',
})

export default docsConfig

pages/+config.ts

import nivel from '@unterberg/nivel/vike'
import type { Config } from 'vike/types'
import vikeReact from 'vike-react/config'
import docsConfig from './+docs'

export { config }

const themePreference = docsConfig.theme?.defaultPreference ?? 'light'
const dataTheme =
  themePreference === 'dark'
    ? (docsConfig.theme?.dark ?? 'consumer-dark')
    : (docsConfig.theme?.light ?? 'consumer-light')

const config: Config = {
  ...nivel,
  extends: [vikeReact],
  title: docsConfig.siteTitle,
  description: docsConfig.siteDescription ?? `${docsConfig.siteTitle} documentation`,
  htmlAttributes: { 'data-theme': dataTheme },
  passToClient: ['docs'],
  prerender: true,
}

vite.config.ts

import { nivelTailwindVite } from '@unterberg/nivel/tailwind'
import vike from 'vike/plugin'

process.env.VIKE_CRAWL ??= JSON.stringify({ git: false })

export default {
  plugins: [nivelTailwindVite(), vike()],
}

pages/+Head.tsx

import { MetaHead } from '@unterberg/nivel/client'

export const Head = () => {
  return <MetaHead />
}

pages/+Layout.tsx

import { AppLayout } from '@unterberg/nivel/client'
import type { ReactNode } from 'react'

const Layout = ({ children }: { children: ReactNode }) => {
  return <AppLayout>{children}</AppLayout>
}

export default Layout

pages/+Wrapper.tsx

import type { ReactNode } from 'react'
import '../styles/global.css'

const Wrapper = ({ children }: { children: ReactNode }) => {
  return <>{children}</>
}

export default Wrapper

styles/global.css

@import '@unterberg/nivel/tailwind.css';
@import './theme.css';

@source '../pages';
@source '../docs';

CLI

nivel init [--root <path>] [--force]
nivel prepare [--root <path>]
nivel --help
  • nivel init scaffolds the visible consumer files and patches the standard docs scripts in package.json
  • nivel init --force overwrites scaffold-managed files if they already exist
  • nivel prepare reads pages/+docs.ts and generates pages/(nivel-generated)

nivel init does not create or overwrite your brand assets or consumer-specific styling decisions beyond the initial scaffold. Theme and palette files stay consumer-owned.

Public Entry Points

| Entry | Purpose | | --- | --- | | @unterberg/nivel | main types, docs helpers, MDX components, shared utilities | | @unterberg/nivel/config | lean config-time entry for defineDocsConfig() and defineDocsGraph() | | @unterberg/nivel/vike | engine-owned Vike config for the consumer's pages/+config.ts | | @unterberg/nivel/client | AppLayout, MetaHead, UserSettingsSync, DocsPage, and client stores | | @unterberg/nivel/mdx | MDX provider entry | | @unterberg/nivel/mdx/code-blocks | code-block components and transforms | | @unterberg/nivel/tailwind | nivelTailwindVite() helper | | @unterberg/nivel/daisyui-theme | daisyUI theme plugin surface | | @unterberg/nivel/runtime/node | lower-level runtime helpers for loading config, resolving docs, scaffolding, and codegen | | @unterberg/nivel/runtime/client | lower-level client runtime entry |

Notes

  • basePath controls the public docs route prefix.
  • contentDir is optional and defaults to docs.
  • If you configure Algolia, apiKey must be a browser-safe search key.
  • The repo validates this package through both the in-repo consumer at packages/consumer-dev and the standalone fixture at tests/npm-consumer.