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

@tacohitbox/bing-scraper

v1.0.4

Published

Scrape results from Microsoft Bing.

Downloads

4

Readme

bing-scraper

Scrape results from Microsoft Bing.

Partially based on @n0rmancodes/bing-scraper.

install

npm i @tacohitbox/bing-scraper

sample code

// Logs results or error.

var bing = require('@tacohitbox/bing-scraper');
bing.search({
  q: 'test',
  pageCount: 2
}, function(err, resp) {
  if (err) {
    console.log(err);
  } else {
    console.log(resp);
  }
});

usage

bing.search(query, cb)

query setting

query can be either a string or object.

You can set userAgent, referer, cookies (must be from a response), lang to request Bing with as well.

You can also set how many pages to grab with pageCount,as well as forcing a language to search (set by lang, by default "en-US") by setting enforceLanguage to true.

example (with object)
{
  "q": "test",
  "userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:87.0) Gecko/20100101 Firefox/87.0",
  "lang": "en-US",
  "referer": "https://www.bing.com/",
  "enforceLanguage": false
  "pageCount": 1,
  "cookies": [
    {
      name: 'MUID',
      value: '1127A942078D62811E16B9C0065963C3',
      domain: '.bing.com',
      expires: 2022-08-22T08:03:58.000Z,
      path: '/',
      secure: true,
      sameSite: 'None'
    }
  ]
}

Cookies are generated by the set-cookie-parser package to keep track of cookies given off by Bing.

You can skip using an object by simply typing the query as a string like bing.search("test").

cb setting

cb must be a function with an error and response variable, like this:

bing.search("test", function(err, res) {
  // Function here.
})

bing.searchImages(query, callback)

This is nearly identical to how query and callback are set.

The exception for this is enforceLanguage in query does nothing.