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

frizzle

v0.0.1

Published

a nextbus client for javascript.

Downloads

4

Readme

frizzle

a simple nextbus api in javascript

es6 note

right now this just works for es6 syntax so its kinda useless, the intent is to use babel to transpile this and get to a es5 compatible module and in-browser version real soon. this was my first try at es6 so thats why its in that syntax

is this name dumb?

you guys get this is a magic schoolbus reference right? right?

install (from git, cause its not on npm quite yet)

$ npm install --save git://github.com/kdoh/frizzle

import and basic instantiation

this is pretty primitive right now and would only really work in an es6 env, but it handles all the major functions for interfacting wtih nextbus

import frizzle from 'frizzle'

/* create a new instance of frizzle with a specified agency. otherwise it defaults to sf-muni cause thats where I live */
let frizzle = new Frizzle({
  agency: 'sf-muni'
})

methods and usage example

/*
  assuming an instantiated class named 'frizzle' like you see above
*/

/* callback, what for to do something with the results from each api function */
let handleNextBusResponse = (result, error) => {
  console.log(result)
  // do other stuff!
}

/* get all the nextbus agencies */
frizzle.agencyList().done(handleNextBusResponse)

/* get all the routes for a given agency */
frizzle.routeList.done(handleNextBusResponse)

/*
  get all information about a route.
  optional param r: stands for the tag of the route if it
  wasn't part of the creation
  
  here we're getting information about the 'F-Market and Wharves' 
  line in San Francisco
*/
frizzle.routeConfig({
  r: 'F'
}).done(handleNextBusResponse)

/*
  get predictions for a given spot
  (s: <string> of stop id)
  on a given route...
  (r: <string> of agency route) if you didn't already specify it
  
  here, we get all info for 'The Embarcadero & Bay' St station towards
  'Castro Station via Downtown' on the 'F-Market and Wharves' line
*/
frizzle.predictions({
  s: '4502',
  r: 'F'
}.done(handleNextBusResponse)

kudos

  • to Nirav Sanghani for derping around on this together and collectively figuring out the nextbus API
  • Designer Fund and my Bridge buddies for the amazing trip to Costanoa, where I ended up hacking on this

project goals

its worth nothing I'm not necessarily looking to make a 'rock solid' library for Nextbus (the es6 usage probably gives that away) and am using this more as an exploratory project. the basic goals are...

  • explore es6
  • provide a decent javascript interface to the NextBus XML API in javascript
  • explore API patterns
  • create a simple API interface to use for React project examples

that being said, I'll try not to be a dick and push breaking changes