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

websbrowser

v1.0.12

Published

## 1 - First let's start by installing the module

Downloads

17

Readme

Usage

1 - First let's start by installing the module

npm install antibotbrowser

2 - Let's include our module in our project

const antibotbrowser = require("antibotbrowser");

3 - And let's run our browser

antibrowser = antibotbrowser.startbrowser();

END - Connect the browser to puppeteer with websocket

const antibotbrowser = require("antibotbrowser");
const puppeteer = require("puppeteer");

(async () => {
  const antibrowser = await antibotbrowser.startbrowser();

  const browser = await puppeteer.connect({
    browserWSEndpoint: antibrowser.websokcet,
  });

  // Normal use from now on
  const page = await browser.newPage();

  await page.setViewport({ width: 0, height: 0 });

  page.goto("https://google.com");
})();

Example uses

1-

const antibotbrowser = require("antibotbrowser");
const puppeteer = require("puppeteer");
(async () => {
  const antibrowser = await antibotbrowser.startbrowser(); // We start the browser with default settings. Port: 9222 Url: google.com

  const browser = await puppeteer.connect({
    browserWSEndpoint: antibrowser.websokcet,
  }); // We connect the launched browser to puppeteer. With the variable we created above, it gives the web socket url to puppetter with antibotbrowser.websocket  .

  // Normal use from now on
  const page = await browser.newPage();

  await page.setViewport({ width: 0, height: 0 });

  page.goto("https://google.com");
})();

Arguments

antibotbrowser.startbrowser(port, url);
// port: The debugging port is the debugging port of the chromium browser. There can be 1 browser on the same port number, so you can add it as an argument. By default, if you enter nothing, the port is 9222.

// url: The first page address on browser startup. If you leave it blank, it defaults to google.com.

// Examples
antibotbrowser.startbrowser(9223, "https://github.com");
antibotbrowser.startbrowser(9222, "https://google.com");
// note do not start 2 scanners on the same port!!!