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

scrapeurl

v1.0.3

Published

A simple nodejs web scraper util that is more capable of scraping sites with anti-scraper functionality.

Downloads

11

Readme

node-scrapeurl

A simple nodejs web scraper util that is more capable of scraping sites with anti-scraper functionality.

introduction

scrapeurl is a web scrape util base on superagent to make requests and iconv-lite to support more charset of web pages. What scrapeurl does is to do the useragent-switching-like things under the hook, and express you a simple api. scrapeurl makes web scraping effective and harder be detected.

installation

npm install scrapeurl

features

  • Do useragent switching, ip switching(change 'X_FORWARDED_FOR' header),referer switching and so on under the hook. Make scraping harder be detected.
  • Charset support. Scrape charset=gbk like web pages easier.

usage

you use scrapeurl as below: scrapeurl(config,callback).done(doneCallback).fail(failCallback)

  • config is an object as:
{
    url:'your url', //require
    delay:1000,//optional defaults to 0, delay by millisecond,
    retry:3,//optional defaults to 0, retry times if error when scraping the url
    charset:'utf8',//optional defaults to null
    userAgent:'custom useragent',//optional defaults to random agent generate by scrapeurl
    ip:'custom ip',//optional defaults to random ip generate by scrapeurl
    referer:'custom referer',//optional defaults to random referer generate by scrapeurl
}

scrapeurl use iconv-lite to do the charset conversion, all supported encoding can be found in iconv-lite

  • callback will receive two auguments as callback(err,response).scrapeurl is based on superagent, and the err and respone are coming from superagent,you may refer to superagent for more details.

  • doneCallback will be called when the scraping succeeds as doneCallback(response)

  • failCallback will be called when the scraping fails as failCallback(err,response)

example

 const scrapeurl = require('scrapeurl')
 scrapeurl({
    url:'your url'
    },function(err,response){
        //do your thing with the response
    })

you may also use it with done and fail :

 const scrapeurl = require('scrapeurl')
 scrapeurl({
    url:'your url'
    }).done(function(response){
        //success code
    }).fail(function(err,response){
        //fail code
    })

notes

Most of the time, you don't have to specify charset in the config, but when you are scraping a Chinese web page with charset=gb2312 or charset=gbk in the meta tag, if you don't specify charset:'gbk' in the config, the response text you scrapes will mess up with the wrong encoding. Since scrapeurl use the parse api of superagent to do the charset job,if you specify charset in the config, the reponse.body will not be available.

dependencies

superagent iconv-lite