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

@exmg/exm-navigation

v1.2.8

Published

```bash npm install @exmg/exm-navigation ```

Readme

<exm-navigation> Published on npm

@exmg/exm-navigation

Install

npm install @exmg/exm-navigation

Anatomy

This library contains following component:

  1. Navigation (main component and fully composed navigation component)

Conceptual usage:

  <exm-navigation .items=${menuItems} .path=${['spaces']}>
    <!-- Slot for adding a title to the topbar. Topbar is only visible on mobile -->
    <section slot="topbar-title">My Title</section>
    <!-- Slot for adding actions to the right of the topbar. Topbar is only visible on mobile -->
    <section slot="topbar-actions">Actions</section>
    <!-- Slot for adding a logo in the top part of the rail. This is not visible on mobile -->
    <section slot="rail-top">Rail top</section>
    <!-- Slot for adding extra actions or other content to the bottom of the rail. This is not visible on mobile -->
    <section slot="rail-bottom">Rail bottom</section>
    <!-- The actual page content to display -->
    <section class="content">${this.renderPage()}</section>
  </exm-navigation>

Some of the components used in the navigation c an be used separately. Please check the code for implementation

API

Slots

| Name | Description | | ---------------- | ------------------------------------------------------------------------------------------------------- | | topbar-title | Slot for adding a title to the topbar. Topbar is only visible on mobile | | topbar-actions | Slot for adding actions to the right of the topbar. Topbar is only visible on mobile | | rail-top | Slot for adding a logo in the top part of the rail. This is not visible on mobile | | rail-bottom | Slot for adding extra actions or other content to the bottom of the rail. This is not visible on mobile | | default | The actual page content to display |

Properties/Attributes

| Name | Type | Default | Description | | -------------------- | ------------ | ------- | ------------------------------------------------------------------------------------------ | | items | MenuItem[] | [] | The list of menuitems to display in the navigation component | | path | string[] | [] | The current/initial path for the navigation | | disable-navigation | boolean | false | Disable navigation managed by the component. In that case you can use the event to trigger |

MenuItem

interface MenuItem {
  id: string;
  label: string;
  type?: 'separator' | 'default';
  path?: string;
  additionalPath?: Regexp;
  url?: string;
  icon?: string;
  items?: MenuItem[];
}

Events

| Name | Detail | Description | | ------------------- | ---------------- | ----------------------------------- | | navigation-change | ['one', 'two'] | The path selected in the navigation |