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

@nanoviews/router

v1.1.0

Published

Nanoviews integration for @nano_kit/router.

Readme

@nanoviews/router

ESM-only package NPM version Dependencies status Install size Build status Coverage status

Nanoviews integration for @nano_kit/router: pages, nested layouts, code splitting, links and head management, with or without dependency injection.

  • Small. Around 1.3 kB (minified and brotlied) on top of the router, and only what you import of it.
  • Direct DOM. A layout is built once and the matched page is swapped inside it.
  • Type-safe. Route names and params are checked in links and path builders.

Installation

pnpm add nanoviews @nano_kit/store @nano_kit/router @nanoviews/router
# or
npm i nanoviews @nano_kit/store @nano_kit/router @nanoviews/router
# or
yarn add nanoviews @nano_kit/store @nano_kit/router @nanoviews/router

Quick Start

@nanoviews/router re-exports everything from @nano_kit/router, so the whole router is imported from it. Here is an app with two pages in a layout, each page in a chunk of its own:

import { mount, main, nav, component$ } from 'nanoviews'
import { browserNavigation, buildPaths, linkComponent, router, pageView, page, layout, loadable, Outlet } from '@nanoviews/router'

const routes = {
  home: '/',
  user: '/users/:id'
} as const
const [$location, navigation] = browserNavigation(routes)
const Link = linkComponent(navigation, buildPaths(routes))

const MainLayout = component$(() => (
  main()(
    nav()(
      Link({
        to: 'home'
      })(
        'Home'
      ),
      Link({
        to: 'user',
        params: {
          id: 1
        }
      })(
        'User'
      )
    ),
    Outlet()
  )
))

const $page = router($location, [
  layout(MainLayout, [
    page('home', loadable(() => import('./pages/Home.js'))),
    page('user', loadable(() => import('./pages/User.js')))
  ])
])

mount(() => pageView($page), document.querySelector('#app')!)

A page module exports its page as default:

// pages/Home.ts
import { h1, component$ } from 'nanoviews'

export default component$(() => (
  h1()(
    'Home'
  )
))

Documentation

For comprehensive guides, advanced patterns, and API reference, visit the documentation website.