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

@savant/chrome

v2.1.0

Published

`@savant/chrome` is a library for interacting with Chrome browsers in the cloud.

Downloads

7

Readme

@savant/chrome

@savant/chrome is a library for interacting with Chrome browsers in the cloud.

DOM

The DOM is auto pruned to only include the following elements:

  • buttons
  • inputs
  • links

The DOM can be access by calling

const pageDom = browser.page;

An example page DOM looks like this:

{
    url: 'https://www.google.com/',
    links: {
        About: '...',
        Store: '...',
        Gmail: '...',
        Images: '...',
        'Google apps': '...',
        Advertising: '...',
        Business: '...',
        ' How Search works ': '...',
        'Carbon neutral since 2007': '...',
        Privacy: '...',
        Terms: '...'
    },
    buttons: {
      'Search by voice': '<div aria-label="Search by voice" role="button"></div>',
      'Search by image': '<div aria-label="Search by image" role="button"></div>',
      'Google Search': '<input value="Google Search" aria-label="Google Search" name="btnK" role="button" type="submit">',
      "I'm Feeling Lucky": `<input id="gbqfbb" value="I'm Feeling Lucky" aria-label="I'm Feeling Lucky" name="btnI" role="button" type="submit">`,
      Settings: '<div role="button"><div jsname="LgbsSe" class="ayzqOc pHiOh" aria-controls="_SuK8Y_LhD7HY5NoP-dqZ6Aw_1" aria-haspopup="true">Settings</div></div>'
    },
    inputs: {
      Search: '<input name="q" type="text" role="combobox" title="Search" value="" aria-label="Search">'
    },
}

Navigation

To navigate to the page, use the goto method.

await browser.goto("yahoo");

To implicitly wait for a page navigation to happen, use the waitForNavigation method.

  • Timesout after 500ms if no navigation initiates
  • Otherwise waits for the navigation to complete
await browser.waitForNavigation();

All page interactions always automatically wait for a page navigation to happen before continuing. This means that you don't need to call waitForNavigation after every action.

Clicking

To click a button, you can use the click method. This method takes a string as an argument, which is the name of the button or input you want to click. The target element will automatically come into view before clicking.

await browser.click("Search Button");

Typing

To type in a <input> you can use the type method. This method takes two arguments: the name of the input you want to type in, and the text you want to type. The target element will automatically come into view before typing.

await browser.type("Search Input", "puppeteer");

Usage

(async () => {
    const Browser = require("@savant/chrome")("URL", apiKey: "", doLog: true);

    const browser = await Browser.launch({});
    await browser.goto("google");
    await browser.type("input[name='q']", "puppeteer");
    await browser.click("input[name='btnK']");
    await browser.waitForNavigation();
    console.log("Done!");
})();