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

chrome-tab

v1.1.0

Published

Sugar for Chrome's remote debugging protocol

Downloads

5

Readme

chrome-tab

Sugar for Chrome's remote debugging protocol.

Why

Phantom's cool but it's hard to get your hands on a binary. Also why not just use a real browser?

How

JSON-RPC over a WebSocket. This is the same interface devtools uses to talk to Chrome - check out the API here.

Example

var Tab = require('./')
var Emitter = require('events')

var tab = new Tab()

process.on('SIGINT', () => {
  tab.close(process.exit)
})

tab.open(err => {
  if (err) throw err

  var events = new Emitter()

  // use rpc-engine's default method to catch any incoming notifications
  tab.defaultMethod = (name, params) => {
    events.emit(name, params)
  }

  // open the Page and Network notification firehoses
  tab.call('Page.enable', err => {})
  tab.call('Network.enable', err => {})

  // wait for Page.frameNavigated
  events.once('Page.frameNavigated', (params) => {
    console.log('Page.frameNavigated', params)

    // use Runtime.execute to run some js to dump the document's outerHTML
    tab.call('Runtime.evaluate', {
      expression: 'document.documentElement.outerHTML',
      returnByValue: true
    }, (err, result) => {
      console.log(result.result.value)
    })
  })

  tab.call('Page.navigate', {
    url: 'https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/websocket-server'
  }, err => {})
})

License

Public domain