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

@real-router/ssr-data-plugin

v0.1.2

Published

SSR per-route data loading plugin for Real-Router

Readme

@real-router/ssr-data-plugin

npm npm downloads bundle size License: MIT

Per-route data loading for SSR with Real-Router. Intercepts start() to load data before server rendering.

// Without plugin:
const state = await router.start(url);
const data = await loadRouteData(state.name, state.params); // manual

// With plugin:
router.usePlugin(ssrDataPluginFactory(loaders));
const state = await router.start(url);
const data = router.getRouteData(); // loaded automatically

Installation

npm install @real-router/ssr-data-plugin

Peer dependency: @real-router/core

Quick Start

import { createRouter } from "@real-router/core";
import { cloneRouter } from "@real-router/core/api";
import { ssrDataPluginFactory } from "@real-router/ssr-data-plugin";

const loaders = {
  "users.profile": async (params) => fetchUser(params.id),
  "users.list": async () => fetchUsers(),
};

// Base router — created once
const baseRouter = createRouter(routes, { defaultRoute: "home", allowNotFound: true });

// Per-request SSR
const router = cloneRouter(baseRouter, { isAuthenticated: true });
router.usePlugin(ssrDataPluginFactory(loaders));

const state = await router.start(url);
const data = router.getRouteData(); // data loaded by matching loader

const html = renderToString(<App />);
router.dispose();

Configuration

Loaders are keyed by route name (not path). Each loader receives route params and returns a Promise:

import type { DataLoaderMap } from "@real-router/ssr-data-plugin";

const loaders: DataLoaderMap = {
  home: async () => ({ featured: await fetchFeatured() }),
  "users.profile": async (params) => ({ user: await fetchUser(params.id) }),
  "users.list": async () => ({ users: await fetchUsers() }),
};

Routes without a matching loader produce no data — getRouteData() returns null.

Router Extension

The plugin extends the router instance with one method via extendRouter():

| Method | Returns | Description | | ---------------------- | --------- | ------------------------------------------ | | getRouteData(state?) | unknown | Get loaded data for current or given state |

router.getRouteData(); // data for current state
router.getRouteData(state); // data for a specific state

SSR-Only by Design

This plugin intercepts start() only — not navigate(). In SSR, the flow is:

cloneRouter → usePlugin → start(url) → data loaded → renderToString → getRouteData()

Client-side navigation and data fetching is the application's responsibility (React Query, Suspense, useEffect, etc.).

Cleanup

const unsubscribe = router.usePlugin(ssrDataPluginFactory(loaders));

// Later — removes getRouteData and stops data loading
unsubscribe();

In SSR, router.dispose() handles cleanup automatically.

Documentation

Related Packages

| Package | Description | | ---------------------------------------------------------------------------------------- | -------------------------------------- | | @real-router/core | Core router (required peer dependency) | | @real-router/browser-plugin | Browser History API integration | | @real-router/react | React bindings |

License

MIT © Oleg Ivanov