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 🙏

© 2026 – Pkg Stats / Ryan Hefner

docparse-scraped-parser

v1.0.19

Published

Server for parsing documents scraped from supplier websites

Readme

Supplier Bill Parser

Parse bills scraped from a supplier website into bill and invoice documents. This module provides the general framework for setting up a supplier-specific parser in the docparse system. Each supplier-specific module will need to implement the actual parsing. This module subscribes the the changes feed and calls the supplier-specific parsing code when a new document is found

Role

Each supplier parser is registered with seaport under the role parseScrapedFGS where FGS is the supplier code

Server

When the parsing service starts up, it setups up a simple express server that reponds to post requests at the /parse/:scrapedID route. The service registers with seaport using the role role parseScrapedFGS. Seaport sends back a port and the parser server listens on this port

Parsing

To parse a scraped document, issue a post http request to the /parse/:scrapedID route at the appropriate host and port, where :scrapedID is the _id of a scraped document in the database

var should = require('should')
var seaport = require('seaport')
var seaConfig = config.get('seaport')
var seaHost = seaConfig.host
var seaPort = seaConfig.port
var ports = seaport.connect(seaHost, seaPort)
var role = 'parseScrapedNGA'
var services = ports.query(role)
services.length.should.be.above(0, 'failed to parse scraped document, no services registered with the role parseScrapedNGA')
var service = services[0]
var serviceHost = service.host
var servicePort = service.port
var url = 'http://' + serviceHost + ':' + servicePort + '/parse/' + scrapedID
var opts = {
  json: true,
  url: url,
  method: 'post'
}
request(opts, function (err, res, body) {
  if (err) {
    console.log(err.stack)
    delete err.stack
    inspect(err, 'error requesting parse via post request to service with role parseScrapedNGA')
    return
  }
  inspect(body, 'parsed scraped NGA document correctly')
})