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

opnr

v1.0.4

Published

launches the browser when ndjson criteria is met

Downloads

18

Readme

opnr

experimental

Sniffs process.stdin for ndjson and launches the browser when a message with url and type: 'connect' is consumed.

It looks for JSON objects with the following format:

{ type: 'connect', url: 'some-page.com' }

URLs are parsed as addresses, so the above opens the default browser to http://some-page.com/. You can configure the action to listen for with the --type field.

This can be used alongside ndjson-emitting CLI tools, like budo:

# launch the browser once an available port is found
budo index.js | opnr

Usage

NPM

Usage:
  opnr [opts]

Opts:
  --type    the "type" to launch on, defualt "connect"

Example

A common scenario might be an async action triggered by a CLI tool that involves a browser launch.

server.js

var http = require('http')

//get next available port
require('getport')(function(err, port) {
  if (err) 
    throw err

  //start your server
  var server = http.createServer(function(req, res) {
    res.end('hello')
  })
  server.listen(port, function(err) {
    if (err)
      throw err

    //print ndjson logs
    console.log(JSON.stringify({ 
      url: 'localhost:'+port, 
      type: 'connect',
      name: 'my-server',
      message: 'server running on '+port 
    }))
  })
})

Install opnr, and optionally garnish for prettier logs.

npm install opnr garnish -g

Now you can pipe things together to run your server and open the browser when ready.

node server.js | opnr | garnish

License

MIT, see LICENSE.md for details.