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

launchpadlite

v0.3.5

Published

You can launch browsers! From NodeJS!

Downloads

6

Readme

LaunchpadLite

You can launch browsers! With NodeJS!

  • Local browsers for MacOS, Windows and Linux (like) operating systems

This is a fork of Launchpad paired down just for my needs.

Rational

I only need to launch a browser for the user to view a page, not for testing. I didn't want to start from scratch beceause I knew there's likely lots of little issues I'm not aware of.

But, that also means much of the functionality of the original launchpad was stuff I didn't need.

I found a few issues. It didn't work in my XP. The code expected LOCALAPPDATA but for whatever reason on my XP there's only APPDATA. It also didn't work on my Windows 8.1. I don't know what the issue was but removing the version checking code fixed that. ShowVer.exe which they included runs on Windows 8.1 but I didn't need any version info so I just ripped that out.

I removed all the code related to checking for the browser already running.

I also needed the option to launch the user's default browser so I added that it. It's identified as "default".

It's down from 43k lines of dependencies to 3.7k lines of which 3k are the underscore and q npm modules.

API

var launch = require('launchpad');
var optionsPassedToChildProcessSpawn = {
  detach: true, // If you want to be able to exit node without killing the browser.
};

launch.local(optionsPassedToChildProcessSpawn, function(error, launcher) {
  launcher.browsers(function(error, browsers) {
    // -> List of available browsers
    browsers.forEach(function(browser) {
      console.log(browser.name);
    });
  });

  launcher[<browsername>](url, function(error, instance) {
    instance.id // -> unique instance id
    instance.stop(callback) // -> Stop the instance
    instance.status(callback) // -> Get status information about the instance
  });
});