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 🙏

© 2026 – Pkg Stats / Ryan Hefner

run-in-browser

v0.2.1

Published

A simple script that will allow you to run code in a browser and then send back a payload of data.

Readme

Run in Browser

A simple script that will allow you to run code in a browser and then send back a payload of data.

RunInBrowser is a function that is a constructor essentially creating a number of differnt run is browser instances each with their own server. It takes one argument a options object that will be passed to either the server created for messaging between browser windows or passed to browser-launcher.

var RunInBrowser = require( 'run-in-browser' ),
    browser = new RunInBrowser( { port: 9999, browser: 'chrome' } );

RunInBrowser::require

RunInBrowser::require is a function that takes a string argument of a file to run in a browser. This is sort of like the relation ship between a web worker. That will open up a browser window ( even a headless browser ). Then it will browserify the code given and run it on the browser.

browser.require( './client' ); // opens browser

When another browser.require happens the first window will exit. ( This is temporary hopefully it will be able to manage multiple windows )

##RunInBrowser::on

Event emitter on method that listens for events from the browser.

RunInBrowser::emit

Send an event to the browser.

RunInBrowser::kill

Kill the browser that is open.

In Browser

Server

So once some code is ran in the browser there is an module that can be required communicate back to the server

var server = require( 'server' );

Server is a basic event emitter that is built to communicate between a browser and the server that opened the browser.

Server::on

Bind to an event that will come from the server

Server::emit

Send an event to the server, there are some limitations on payload, just about anything will work except funcitions and DOM stuff.