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

@remix-run/spa

v1.0.1

Published

Client-rendered application routing for Remix

Readme

spa

Client-rendered application routing for Remix. It connects a standard fetch router to the browser component runtime without exposing the response carrier used to associate route responses with Remix nodes.

Features

  • Standard fetch routing - Preserve Request to Response dispatch, redirects, status codes, headers, middleware, and cancellation
  • Node rendering middleware - Render RemixNode values through context.render()
  • Browser runtime - Resolve the current URL and future frame navigations through the router
  • Initial fallback - Display an interactive Remix node while the first route loads

Installation

npm i remix

Usage

Install render() before middleware and route handlers that use context.render(), then pass the router to run().

import { createRouter } from 'remix/router'
import { get, route } from 'remix/routes'
import { render, run } from 'remix/spa'

const routes = route({
  home: get('/'),
  about: get('/about'),
})

const router = createRouter({
  middleware: [render()],
  defaultHandler({ render }) {
    return render(<h1>Not Found</h1>, { status: 404 })
  },
})

router.map(routes, {
  actions: {
    home({ render }) {
      return render(<h1>Home</h1>)
    },
    about({ render }) {
      return render(<h1>About</h1>)
    },
  },
})

const app = run(router, { fallback: <p>Loading…</p> })
await app.ready()

The router remains an ordinary fetch router, so its normal actions, controllers, middleware, and context typing continue to apply.

Wrapping Route Content

Pass a request-aware transform to render() when every route should share an application shell.

const router = createRouter({
  middleware: [
    render((content, { url }) => (
      <main data-pathname={url.pathname}>
        <nav>{/* ... */}</nav>
        {content}
      </main>
    )),
  ],
})

Related Packages

Related Work

  • Fetch standard - The request and response model preserved by SPA routers
  • Navigation API - Browser navigation lifecycle used by the Remix component runtime

License

See LICENSE