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

wscriptlauncher

v0.3.16

Published

Provides a simple human-machine, machine-machine interfaces to run a script file on a platform of interest and get output to your terminal

Downloads

39

Readme

wScriptLauncher Build Status BrowserStack Status

wScriptLauncher provides a simple human-machine, machine-machine interfaces to run a script file on a platform of interest and get output to your terminal. The platform could be remote or local, browser or native. Platforms list could be extended by an implementation of a new custom platform provider.

Implemented platforms :

Name - platform option value

Installation

npm install wscriptlauncher

Usage options

Option | Type | Optional | Default | Description ------------------------- | -------------------------| -------------------------| :------------------------- | ------------------------- filePath |string || |path to script file platform |string||chrome| sets target platfrom headless |boolean||true| run in headless mode terminatingAfter |boolean||true| terminate launcher after script execution verbosity |number||1| sets level of details of console output

Usage with Nodejs:

var _ = wTools;

/* Initialize launcher with provided options object */

var launcher = wScriptLauncher
({
  filePath : '/path/to/file',
  headless : true,
  platform : 'chrome',
  terminatingAfter : true,
  verbosity : 1
});

/* Run our script file on target platform by calling launch, it
   returns wConsequence object which gives us a message with platform provider
   when all work will be done. More about wConsequence - https://github.com/Wandalen/wConsequence
*/

launcher.launch()
.got( function ( err, provider )
{
  if( err )
  throw _.errLog( err );

  console.log( provider );
});

Sample here.

Usage with command line:

To print help:

launcher

To run script with default setting:

launcher /path/to/file.js

To run script with options, first argument must be path:

launcher /path/to/file.js platform : chrome headless : 0 terminatingAfter : 1

Another way to run script with options:

launcher filePath : /path/to/file.js platform : firefox headless : 1

Acknowledgements

We would like to thank Browserstack for support!