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

mirrorconsole

v0.1.2

Published

debug webapps on mobile easily

Downloads

16

Readme

mirrorConsole

Debug webapps on mobile devices without connecting them to a computer (and more importantly, debug an iPhone without a Mac).

Installation

  • Clone this repo
  • run npm install

Run the servers

  • Run npm run HTTP
  • A simple HTTP server will start, it will be used to serve the Javascript to the client - note the ip addresses suggested.
  • Run npm run WS
  • The websocket server will be launched and start listening for the incoming console messages.

Set up the client

  • In the head of the HTML file you need to debug copy <script src="http://<one-of-the-ips-suggested-by-the-HTTP-server>:9998/client.js"></script>
  • Serve it how you normally do through a web server and you start seeing flowing logs in the console where you fired the server

Settings

Host

You can change the ip address and the port for the websocket server in the config.json file.

Colors

You can change the colors based on the console event (log, info, warn and error), by editing the file config.json. You can find all the color options on the Chalk readme page https://github.com/chalk/chalk.

Troubleshooting

If you don't see the logs flowing in the console as expected, try changing the host ip address from the client.js file to a working one. You can start trying with those suggested by the HTTP server.

// var hostIP = location.host.split(':')[0];
var hostIP = '192.168.1.1';

That's it. If you don't see the colors on Windows, try http://cmder.net/.