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

@pdftron/web-crawler

v0.0.5

Published

Web crawling using Puppeteer

Downloads

9

Readme

Web crawler

A simple NodeJS web crawler that actually executes JS!

BETA - Not for production use

Usage

constructor(options)

const c = new Crawler(options);
  • options <[Object]>
    • debug <[boolean]> Whether to display logs during execution. Defaults to false
    • maxConnections <[number]> Number of simultanious connections that can be open. Defaults to 10

.queue(url)

Adds a URl to the fetch queue

  • url <[string]> URL to start crawling at

.start()

Starts processing the queue

.shouldFetch(callback)

A function that determines if a URL should be fetched or not.

  • callback <[Function(string)]> function that determines if a url is fetched. Is passed the URL to be fetched. Must return true or false. If true is returned, the URL will be fetched.

.on(key, callback)

Attach an event listener to the instance.

  • key <[string]> type of event listener to attach. Can be one of:
    • done Called when the process is done. callback is passed an array of urls found.
    • fetched Called when a page is fully fetched. callback is passed an object with html and url. This is the only way to get the HTML from a page using the crawler.
    • foundURL Called when a new URL is found and added to the queue. callback is passed the URL and the page the URL was found on.
    • loadError Called when a page can not be fetched. Parameters are the url that cant be fetched, the page the url was found on, and the status code

Example

const Crawler = require('@pdftron/web-crawler');

const c = new Crawler({ debug: false });

c.queue('https://www.pdftron.com/documentation');

c.shouldFetch((url) => {
  return url.indexOf('/documentation') > -1 && url.indexOf('web/guides') > -1;
})

c.on('foundURL', (url, foundOn) => {
  console.log(`${url} was found on ${foundOn}`);
})

c.on('done', (data) => {
  console.log(data);
})

c.on('fetched', ({ url, html }) => {
  console.log(url, html);
})

c.start();

Developing

git clone https://github.com/XodoDocs/web-crawler.git
cd web-crawler
npm i
npm run test