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

wit-router

v0.1.2

Published

A router for wit.ai entities. Rranks a set of entities returned from wit.ai based on criteria that you register.

Readme

wit-router

A router for wit.ai entities. Ranks a set of entities returned from wit.ai based on criteria that you register. Ranking is determined by averaging the 2 ranks for each comparison - how the route request entity set matched against each registered route, and how the registered route matched against the query. This favors matching more specific entity sets in the query rather than simply satisfying 100% of the match criteria of a route, so that a more specific route can be chosen instead of a simpler/less complete route.

Usage

const WitRouter = require('wit-router')
const witRouter = new WitRouter()
witRouter.register({
  name: 'version',
  entities: {
    intent: [{
      match: /^version$/
    }]
  },
  callback: function () {
    console.log('hit version route')
  }
})

witRouter.register({
  name: 'version',
  entities: {
    intent: [{
      match: /^version$/
    }],
    server: [{
      match: /^CVP$/
    }]
  },
  callback: function () {
    console.log('hit CVP version route')
  }
})

witRouter.register({
  name: 'version',
  entities: {
    intent: [{
      match: /^version$/
    }],
    server: [{
      match: /^CVP$/
    }],
    service: [{
      match: /^Call Server$/,
      required: true
    }]
  },
  callback: function () {
    console.log('hit CVP Call Server version route')
  }
})

// route to 'CVP Call Server Version'
witRouter.route({
  service: [{
    confidence: 0.90813538787052,
    value: 'Call Server',
    type: 'value'
  }],
  server: [{
    confidence: 0.93483557193052,
    value: 'CVP',
    type: 'value'
  }],
  intent: [{
    confidence: 0.99982729131181,
    value: 'version'
  }]
}).callback()

// route to 'CVP Version'
witRouter.route({
  server: [{
    confidence: 0.93483557193052,
    value: 'CVP',
    type: 'value'
  }],
  intent: [{
    confidence: 0.99982729131181,
    value: 'version'
  }]
}).callback()

// route to 'version'
witRouter.route({
  intent: [{
    confidence: 0.9884404035283,
    value: 'version'
  }]
}).callback()