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

ots-heading-parser

v0.2.2

Published

Reads the contents of a file from The Sports Network and checks the <heading> element to figure out what type of file it is.

Downloads

11

Readme

Heading Parser for Sports Network Data Files

Looks at a file and spits back what's in the heading element. It's meant to tell you which parser to the parser-proxy needs to spawn in order to store the data.

Options

  • --file: the relative or absolute path to the file of interest
  • --filetype: pbp|other pbp can let us know that we don't need to read the file in and examine the <heading> element because it's a known play by play file.
  • --ignore: Tell the heading parser to ignore a letter in the 2nd position of the heading node. e.g. A, B, J to ignore files having to do with a certain sport.
  • --sport: nfl|mlb if the sport type is already known, specify it here.
  • --delim: Defaults to |||, but you can configure it here. WARNING: If filenames contain the delimiter, weird things can happen.
  • --in0: present or not. If this argument is present, it lets us know that the stdin input is delimited by \0 nulls instead of \n newlines.
  • --out0: present of not. If present, delimit the output with \0 nulls instead of \n newlines.

Input

Can come from either stdin if we're piping a large list of files to the parser or just standard command line options specified above.