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

robots-parser-combinator

v1.1.0

Published

A proper robots.txt parser and combinator that works with eulalie

Downloads

3

Readme

robots-parser-combinator

Build Status

A proper robots.txt parser and combinator that works with eulalie.

Usage

User-agent: *
Allow: /blog/index.html  # site blog
Disallow: /cgi-bin/
Disallow: /tmp/
Sitemap: http://www.mysite.com/sitemaps/profiles-sitemap.xml  # extra profile urls
# save the robots
> const parser = require('robots-parser-combinator')
> const robotstxt = fs.readFileSync('./robots.txt', 'utf8')
>
> var goodRobots = parser.parse(robotstxt)
[ { useragent: { value: '*' } },
  { allow: { value: '/blog/index.html', comment: 'site blog' } },
  { disallow: { value: '/cgi-bin/' } },
  { disallow: { value: '/tmp/' } },
  { sitemap:
     { value: 'http://www.mysite.com/sitemaps/profiles-sitemap.xml',
       comment: 'extra profile urls' } },
  'save the robots' ]

> var badRobots = parser.parse('')
[]

Or you can feed the parser.robotstxt combinator into eulalie to parse robots.txt.

You can also parse robots.txt containing nonstandard extensions like Crawl-delay or Host by using the parser.parseNS function. The combinators for nonstandard extensions are also provided.

Implementation

The parser is an implementation of the BNF form for robots.txt based on the Google spec, and references RFC 1945 and RFC 1808 when appropriate.

LWS (linear-white-space) is defined using the rule specified in RFC 5234, rather than RFC 1945. There is a small but very significant inconsistency between the rules:

RFC 5234 linear-white-space:

WSP  = SP / HTAB
LWSP = *(WSP / CRLF WSP)

RFC 1945 linear-white-space:

LWS = [CRLF] 1*( SP | HT )

The RFC 1945 linear-white-space rule consumes at least one space or tab character, and RFC 5234 does not. Due to this inconsistency, the parser has chosen the more general rule in order to be more flexible. You can set the parser to use the stricter rule by setting parser.setStrictLWS(true) before parsing.

All of the BNF rules in the robots.txt spec are provided as combinators. Since the combinators are compatible with eulalie, you can use them to get partial aspects of a robots.txt file or as part of a larger combinator.

License

Licensed under the MIT license.