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 🙏

© 2025 – Pkg Stats / Ryan Hefner

xdn-router

v1.0.19-upload-assets-to-subaccounts.1

Published

## Overview

Readme

xdn-router

Overview

This package provides a router that allows the developer to declare routes their either run at the edge (for example, proxy and redirect), or defer to next.js's router. You can also create clean routes for next.js.

Configuring Routes

import { Router } from 'xdn'

new Router()
  // redirect at edge
  .match('/some/path/:withVar', ({ redirect }) => {
    redirect('/some/other/path/{withVar}', 301)
  })

  // proxy the origin site
  .match('/some/path/:withVar', ({ proxy }) => {
    proxy('desktop', {
      path: '/some/other/path/{withVar}',
    })
  })

  // match based on header and proxy the origin site
  .match({ headers: { 'xdn-device-type': 'desktop' } }, ({ proxy }) => {
    proxy('desktop')
  })

  // vanity URL for next.js
  .match('/holiday-sale', ({ render }) => {
    render((req, res) => nextRenderFunction(req, res, { productId: 2 }, '/p/[productId]'))
  })

  // OR

  .match('/holiday-sale/:productId', ({ render, params }) => {
    render((req, res) => nextRenderFunction(req, res, params, '/p/[productId]'))
  })

  // Synthetic html response
  .match('/static-html', ({ respond, responseHeaders }) => {
    responseHeaders({ set: { 'Content-Type': 'text/html; charset=UTF-8' } })
    respond('<html><body><h1>Hello world!</h1></body></html>', 200)
  })

  // fall back to next's router
  .fallback(({ render }) => render(nextRenderFunction))

Creating an Outer Edge Manager config

At build time, an outer edge manager config can be derived from the router by calling router.createEdgeConfig().

Example

To run routes example file use any node process manager and run the file as:

  • $ node ./routes.example.js

This example outputs oem.example.json with outer edge configuration and will run on http://127.0.0.1:3001