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 🙏

© 2024 – Pkg Stats / Ryan Hefner

poptart-router

v3.0.0

Published

Client-side router.

Downloads

11

Readme

Some JavaScript client-side router.

Install

With npm do:

npm install poptart-router history --save

You also need the history module.

Usage

var createRouter = require('poptart-router')
var history = require('history')()

var router = createRouter(history)

function callback (location, next) {
  // That is history's location object
  // https://github.com/ReactJSTraining/history/blob/master/docs/Location.md

  var name = location.params.name; // url params
  var foo = location.state.foo; // your state object
  
  console.log(name)
  console.log(foo)
  
  next() // allow the callback chain go forward
}

router.add('/hello/:name', callback)

router.start()

router.push({
  pathname: router.generate('/hello/:name', { name: 'world' })
  state: { foo: 'bar' }
})

// => "world"
// => "bar"

API

createRouter

createRouter(history[, base, callback])

  • history A history object.
  • base (String) should be set in case you're not operating at the root path / of the domain.
  • callback is fired after all callbacks of every matched route have been called. It should follow this signature function (err, location) {}.

#add

router.add(path[, callback...])

You can add as many callbacks as you need. This is internally handled by the ware module, so the callback signature should be the following:

function (location, next) {}

Remember to call next when you're done so the next callback in line can be fired.

Routes are matched in the order they were added, and they are matched using the famous path-to-regexp module, used by Express among many others, so regular expressions are supported and all that.

Please check out the path-to-regexp documentation to know more about route options. Also checkout the live demo!

#route

add alias.

#start

router.start([immediately])

Router starts listening for route changes.

For immediately pass false if you want to skip parsing the current location at start.

#push

router.push(location)

A wrapper around history.push, where location is that one from the history module.

This will update the browser's URL and fire any callbacks.

#replace

router.replace(location)

Same as push but using replaceState...

#stop

router.stop()

Stop listening for changes.

License

MIT