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

@dualmark/nextjs

v0.5.2

Published

Next.js App Router adapter for the Dualmark AEO framework. Drop-in proxy/middleware + route-handler factory + withDualmark() config wrapper. Same API surface as @dualmark/astro.

Readme

@dualmark/nextjs

Next.js App Router adapter for the Dualmark AEO framework.

Same one-line install as @dualmark/astrowithDualmark() for the config, createDualmarkMiddleware() for proxy.ts (or middleware.ts on Next ≤15), createDualmarkRouteHandler() for the markdown twin route handler, and createLlmsTxtHandler() for /llms.txt.

Install

bun add @dualmark/nextjs @dualmark/core @dualmark/converters

Usage

import { withDualmark } from "@dualmark/nextjs";

export default withDualmark(
  { reactStrictMode: true },
  {
    siteUrl: "https://example.com",
    collections: {
      blog: {
        converter: "blog",
        getEntries: () => yourPosts,
      },
    },
    llmsTxt: {
      enabled: true,
      brandName: "Acme",
      sections: [{ title: "Pages", links: [{ title: "Home", href: "/" }] }],
    },
  },
);
import { createDualmarkMiddleware } from "@dualmark/nextjs";

const middleware = createDualmarkMiddleware({
  siteUrl: "https://example.com",
});

export default middleware;
export const config = middleware.config;

On Next.js ≤15, name the file middleware.ts instead. The body is identical.

import { createDualmarkRouteHandler } from "@dualmark/nextjs";
import { POSTS } from "@/lib/posts";

const handler = createDualmarkRouteHandler({
  siteUrl: "https://example.com",
  collections: {
    blog: {
      converter: "blog",
      getEntries: () => POSTS,
    },
  },
  staticPages: [{ pattern: "/", render: () => "# Home\n\nWelcome." }],
});

export const GET = handler.GET;
export const generateStaticParams = handler.generateStaticParams;
export const dynamic = "force-static";
import { createLlmsTxtHandler } from "@dualmark/nextjs";

const handler = createLlmsTxtHandler({
  brandName: "Acme",
  sections: [{ title: "Pages", links: [{ title: "Home", href: "/" }] }],
});

export const GET = handler.GET;
export const dynamic = "force-static";

Architecture

┌─────────────────────────────────────────────────────────────┐
│ proxy.ts                                                    │
│   - if path ends in .md     → rewrite to /md/<path>        │
│   - if AI bot UA OR Accept: text/markdown                   │
│       → rewrite to /md/<path>                               │
│   - if Accept rules out html+md → 406                       │
│   - else (HTML) → next() + Link rel=alternate header        │
└─────────────────────────────────────────────────────────────┘

app/
├── ...your existing pages
├── md/[...path]/route.ts   ← createDualmarkRouteHandler (renders .md)
└── llms.txt/route.ts       ← createLlmsTxtHandler (renders /llms.txt)

/md/... is an internal namespace your users never see — the proxy rewrites to it, and the route handler dispatches to your collections, static pages, or parameterized routes. Configurable via internalNamespace if you need a different name.

Built-in converter names

blog, case-study, changelog, compare, docs, feature, glossary, legal, pricing, pseo, tool, video. Pass any of them as converter, or pass a function (entry) => string for custom output.

Why Next.js needs getEntries

Astro has astro:content to discover collection entries automatically. Next.js has no equivalent — content can come from the filesystem, a CMS, a database, anything. So you supply getEntries: () => Entry[] | Promise<Entry[]> and the adapter does the rest.

License

Apache 2.0