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

scores

v3.9.10

Published

Track the completion of sports games from a URL.

Downloads

64

Readme

scores

Track the completion of sports games from a URL.

NPM Build Status Greenkeeper badge

Usage

const Scores = require("scores")

new Scores({
  url: "http://place-where-scores-are.com",
  interval: "5m", // or a number of ms
  timezone: "America/New_York",
  dailyCutoff: 180, // in minutes,
  completed: { seriesCompleted: true }, // passed to _.filter to decide if an event is completed
  parse: {
    // Is used to try and guess the ending time of the event
    // In this case we are checking for college basketball where
    // there are two 20 minute halves. Eg NBA would be '12m' and 4
    finalPeriod: 2,
    periodLength: "20m", // or a number of ms
  },
})
  // Will be fired on the completion of each game
  .on("event", (game) => console.log(game))
  // Start the watcher
  .start()

How does it work?

It intermittently parses the DOM of the URL to see if any games have been completed. There is also logic for what to do in situations where there are no games that day or none of the games have started, or all the games have finished.

API

new Scores(options)

  • options.interval (Integer, default: 15) Interval in minutes for how often to request the url
  • options.timezone (String, default: 'America/New_York') A moment-timezone string for which timezone you want to base dates off
  • options.dailyCutoff (Integer, default: 180) The amount of minutes after midnight that the date should switch. This allows you to keep checking for the games that might go past midnight.
  • options.url (String) The url to request. {date} will be replaced with today's date as YYYYMMDD
  • options.logger A bucker compatible instance which will log interesting things
  • options.parse (Object) Options that will be passed directly to the parse method

methods

  • start() Start the interval to watch for new games
  • stop() Stop watching

events

  • scores.on('event', event => { ... })
  • scores.on('error', err => { ... })

MIT License