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

@auraui/router

v0.1.0

Published

HTML-first declarative router. Real HTML pages with client navigation (MPA→SPA). Works with plain HTML or Web Components.

Readme

Aura Router

npm version CI bundle size license

HTML-first declarative router for Web Components with nested outlets and route lifecycle. First visit renders a real HTML page; after AuraRouter.install(), in-app navigation updates content without a full reload (MPA→SPA).

npm install @auraui/router

Why Aura Router

| | | | --- | --- | | Routes in HTML | <aura-router>, <aura-route>, <aura-outlet> — path, layout, view, hooks, and cache in markup | | Nested layouts | Shared shell stays mounted; only the matched leaf updates in the outlet | | Route lifecycle | guard, load, ready, leave, unmount, … — including client redirect chains | | Cache & prefetch | Route-scoped cache (view / data / DOM); intent/tap prefetch on in-app links | | HTML-first, MPA → SPA | First visit paints server HTML; later navigations update the outlet without a full reload | | SEO-friendly | Crawlers and link previews read real HTML when the server renders the page — no empty client shell | | Progressive enhancement | Root-absolute hrefs work without JS; aura-router-link upgrades them to client navigation |

Works with plain HTML, vanilla custom elements, or Lit. Load full server pages with url + extract when you need a fragment. See the guide.

Quick start

1. Install

import { AuraRouter } from '@auraui/router';

AuraRouter.install();

Or CDN (pin the version):

<script type="module">
  import { AuraRouter } from 'https://esm.sh/@auraui/[email protected]';
  AuraRouter.install();
</script>

Registers <aura-router>, <aura-route>, and <aura-outlet>.

2. Declare routes

<aura-router>
  <aura-route path="/" view="index.html"></aura-route>
  <aura-route path="/users" view="users.html"></aura-route>
  <aura-route path="/about" view="template::about-page"></aura-route>
  <aura-route path="*" view="template::not-found"></aura-route>
</aura-router>

<template id="about-page">
  <h1>About</h1>
  <p>Static markup or Web Components go here.</p>
</template>

<template id="not-found">
  <h1>404</h1>
</template>

Nested shell (layout stays mounted across children):

<aura-router>
  <aura-route path="/app" layout="app-shell" guard="auth">
    <aura-route path="users" view="users.html" load="users"></aura-route>
    <aura-route path="settings" view="template::settings"></aura-route>
  </aura-route>
  <aura-route path="*" view="template::not-found"></aura-route>
</aura-router>

<template id="app-shell">
  <nav><!-- durable chrome --></nav>
  <aura-outlet></aura-outlet>
</template>

<template id="settings">
  <h1>Settings</h1>
</template>

guard / load are hook names from AuraRouter.use — see lifecycle hooks. A bare view file name (e.g. users.html) is fetched from the server after the first full load.

3. Links

<a href="/" aura-router-link>Home</a>
<a href="/app/users" aura-router-link>Users</a>

Prefer root-absolute paths (/users). Aura matches /users and /users/ as the same route and keeps the pathname as in the link. Same-origin absolute URLs (https://your-host/…) on [aura-router-link] also SPA-navigate; other origins keep a full page load — see How href resolves.

document.querySelector('aura-router')?.navigate('/app/users');

Playground: playground/. Recipes: docs/recipes/.

Browsers

Modern evergreen browsers (Chrome, Firefox, Safari, Edge) with ES modules, Custom Elements, History API, fetch, and URLPattern (for :param routes).

No Internet Explorer. No Node SSR runtime — the router runs in the browser. See LIMITATIONS.

Docs

| | | | --- | --- | | Usage guide | docs/guide.md | | Questions / feedback | GitHub Discussions · [email protected] | | Known gaps | LIMITATIONS.md | | Security | SECURITY.md | | Roadmap | ROADMAP.md | | Changelog | CHANGELOG.md | | Contributing | CONTRIBUTING.md | | npm | @auraui/router |

Stability

Each version before 1.0.0 may include breaking changes — check the CHANGELOG. See ROADMAP.

License

MIT covers source code only — not the project name or logos. See LICENSE and TRADEMARKS.md.