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

@42a/ael-next

v0.1.1

Published

Next.js (App Router) adapter for the 42a Agentic Enablement Layer: markdown page variants, llms.txt and an MCP server for your site in three small files.

Readme

@42a/ael-next

Next.js (App Router) adapter for the 42a Agentic Enablement Layer: markdown page variants, llms.txt, and an on-site MCP server in three small files.

Requires Next.js ≥ 14 with the App Router (Pages Router is not supported).

Install

npm install @42a/ael @42a/ael-next

1. ael.config.ts (project root)

import { defineAelConfig } from "@42a/ael";

export default defineAelConfig({
  siteUrl: "https://example.com",
});

2. middleware.ts

import { createAelMiddleware, AEL_MATCHER } from "@42a/ael-next/middleware";
import aelConfig from "./ael.config";

export const middleware = createAelMiddleware(aelConfig);
export const config = { matcher: AEL_MATCHER };

Already have middleware (Clerk, next-intl, …)? Compose instead:

import { withAel } from "@42a/ael-next/middleware";
export const middleware = withAel(aelConfig, existingMiddleware);

3. app/api/ael/[[...path]]/route.ts

import { createAelRouteHandlers } from "@42a/ael-next";
import aelConfig from "../../../../ael.config";

export const dynamic = "force-dynamic";
export const { GET, POST } = createAelRouteHandlers(aelConfig);

That's it. The middleware rewrites /llms.txt, /llms-full.txt, <path>.md, ?format=markdown, Accept: text/markdown, /.well-known/mcp*, and POST /api/mcp into the route handler, and adds a Link: <…?format=markdown>; rel="alternate" header to your HTML pages so the markdown variants are discoverable — no layout edits.

Verify with:

npx @42a/ael doctor https://example.com

Connect to 42a (optional)

npx @42a/ael connect

Mints a site token; add it as the FORTYTWOA_SITE_TOKEN environment variable and redeploy. Domain verification happens automatically via /.well-known/42a.json.

Notes

  • Runtime: Node by default; the core is edge-clean, so export const runtime = "edge" works too.
  • Caching: llms outputs get s-maxage=43200 (12 h); converted markdown is cached in an in-memory KV per instance (pass cache: in the config for a persistent store).
  • Content: defaults to self-render (sitemap + own HTML). Pass a custom provider for CMS-backed sites — see the @42a/ael README.