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

@unrdf/nextra-docs

v5.0.1

Published

UNRDF documentation with Nextra 4 - Developer-focused Next.js documentation

Readme

@unrdf/nextra-docs

UNRDF documentation site built with Nextra 4.6.1 + Next.js 16.

✅ Status: Working (Webpack Mode)

This package works with Next.js 16.0.7 using Webpack instead of Turbopack.

Solution: Use next build --webpack flag to force Webpack mode Reference: Official Nextra examples use this approach Alternative: Docusaurus 3 (in /apps/docs-site) for production deployment

Features

  • Nextra 4.6.1: Latest version with App Router support
  • Next.js 16.0.7: Latest Next.js with Webpack mode (--webpack flag)
  • React 19.2.1: Latest React
  • TypeScript 5.9.3: Full type safety
  • MDX 3: Advanced markdown with JSX components
  • Search: Built-in full-text search (codeblocks disabled for performance)
  • LaTeX: Math equations support
  • Code Highlighting: Syntax highlighting with copy button

Development

# Install dependencies
pnpm install

# Start dev server (port 3003)
pnpm dev

# Build for production
pnpm build

# Preview production build
pnpm start

Structure

packages/nextra/
├── app/                    # Next.js App Router
│   ├── layout.tsx         # Root layout with theme config
│   ├── page.mdx           # Landing page
│   ├── guides/            # Guides section
│   ├── reference/         # API reference
│   ├── concepts/          # Conceptual docs
│   └── examples/          # Examples
├── components/            # React components
├── public/                # Static assets
├── next.config.mjs        # Next.js + Nextra config
└── tsconfig.json          # TypeScript config

Key Configuration

Webpack vs Turbopack

This package uses Webpack instead of Turbopack:

  • Next.js 16 defaults to Turbopack, but --webpack flag forces Webpack mode
  • Nextra 4.6.1 works correctly with Webpack (official examples use this approach)
  • Theme configuration is passed as props to <Layout> component in app/layout.tsx

Port

Dev server runs on port 3003 (to avoid conflicts with other apps).

Advantages over Docusaurus

  • Next.js Integration: Seamless integration with Next.js apps
  • React Server Components: Modern React patterns
  • Better Performance: Faster page loads with Next.js optimizations
  • Developer Experience: Hot reload, better TypeScript support
  • Component Flexibility: Use any React component in MDX

Deployment

Can be deployed as:

  • Standalone site: Vercel, Netlify, etc.
  • Static export: GitHub Pages (with output: 'export')
  • Next.js server: Any Node.js hosting

Learn More