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 🙏

© 2025 – Pkg Stats / Ryan Hefner

ptmnavigator

v0.1.6

Published

## How to (locally) embed this into another Vue project:

Readme

ptmnavigator

How to (locally) embed this into another Vue project:

  • In this project: configure vue.config.js for library export (it currently already is, so you can copy-paste this for future projects)
  • In the parent project, in the component where you want to load it, use it like this (assuming you have a custom API implemented already)
<template>
    <ptm-navigator
      :backend-api="ptmnavigatorBackend"
      :ptm-navigator-router="router"
    />
</template>

<script>
import { PTMNavigator } from 'ptmnavigator'
import myCustomAPI from '../../plugins/myCustomAPI'

export default {
  name: 'PTMNavigatorWrapper',
  components: {
    'ptm-navigator': PTMNavigator
  },
  data () {
    return {
      ptmnavigatorBackend: ptmNavigatorPrdbApi,
      router: this.$router
    }
  }
}
</script>
  • Then, build PTMNavigator (in frontend package): npm run build (I think you don't have to call npm link from here, but try it out in case it doesn't work).
  • In the main component establish the link with: npm link ptmnavigator

From now on, everytime you make changes and want them to show in your parent component:

  • npm run build (in PTMNavigator/frontend)
  • Shutdown server of the main component
  • rm -rf node_modules/.cache/
  • Restart server with npm run serve

Project setup

npm install

Compiles and hot-reloads for development

npm run serve

Compiles and minifies for production

npm run build

Lints and fixes files

npm run lint

Customize configuration

See Configuration Reference.