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

@gluonjs/router

v1.1.0

Published

The official Gluon router with browser, hash, and memory histories.

Readme

The official Gluon router provides deterministic route matching, browser/hash/ memory histories, typed named routes, guards, failures, lazy route components, scroll restoration, and Gluon application bindings.

The package is part of the lockstep Gluon 1.1.0 release line. Core and Reactivity are peers so an application has one shared application context and reactive identity.

Browser application

import { createApp, html } from '@gluonjs/core';
import {
  RouterLink,
  RouterView,
  createRouter,
  createRouterPlugin,
  createWebHistory,
  lazyRoute,
} from '@gluonjs/router';

const router = createRouter({
  history: createWebHistory('/app'),
  routes: [
    { path: '/', name: 'home', component: () => html`<h1>Home</h1>` },
    {
      path: '/reports/:id',
      name: 'report',
      component: lazyRoute(() => import('./report-page.js')),
    },
  ],
  scrollBehavior: (_to, _from, saved) => saved ?? { left: 0, top: 0 },
});

await router.isReady();

const app = createApp(() => html`
  ${RouterLink({ to: '/', children: 'Home' })}
  ${RouterView()}
`);
app.use(createRouterPlugin(router));
app.mount(document.querySelector('#app')!);

RouterLink intercepts unmodified same-context clicks and exposes active and exact-active classes. RouterView({ depth, name }) selects nested and named route components. Unmounting the application destroys the installed router.

Typed named routes

type Routes = {
  home: { params: {} };
  report: { params: { id: string | number } };
};

const typedRouter = createRouter<Routes>({ history, routes });
await typedRouter.push({ name: 'report', params: { id: 42 } });

Path params are encoded on generation and decoded on matching. Query keys are sorted during serialization; repeated values retain their input order. Prototype-like decoded keys remain frozen own data and never participate in the parser accumulator's prototype chain.

Navigation control

beforeEach, record beforeEnter, and beforeResolve run in that order. Returning false aborts navigation; returning a location redirects it. push and replace resolve with an aborted, cancelled, or duplicated NavigationFailure when applicable. Loader and hook errors reject navigation and are forwarded to onError handlers.

Lazy routes must use lazyRoute(() => import(...)). The explicit wrapper keeps ordinary functional components unambiguous and preserves production code splitting.

Memory and server use

Import @gluonjs/router/memory in Node, tests, or server rendering code. This entry point has no browser-history or Gluon UI binding export.

import { createMemoryHistory, createRouter } from '@gluonjs/router/memory';

const router = createRouter({
  history: createMemoryHistory(['/reports/42?print=true']),
  routes,
});
await router.isReady();

const snapshot = router.dehydrate();
await browserRouter.hydrate(snapshot);

See the repository router contract for route syntax, history ownership, SSR handoff, failure, and scroll behavior.

License

MIT License, Copyright © 2026 Marc Malerei.