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

npm-script

v1.2.0

Published

NPM run-script spawning options generator

Downloads

45

Readme

npm-script

Generate spawn options for running package.json scripts

Example

Emulates npm run-script $SCRIPT_NAME

**NOTE: ** Does not add in the log wrapping like NPM

var lifecycle = process.argv[2];
getNPMSpawnOptions(process.cwd(), lifecycle, {
  defaultScript: {
    start: 'node server.js',
    preinstall: '[ -f wscript] && (node-waf clean || true; node-waf configure build)'
  }[lifecycle],
  env: {
    PATH: process.env.PATH
  },
  fs?: fs_api // defaults to require('fs') used for remote system stuff
}, function (err, spawnOptions) {
  var script = require('child_process').spawn.apply(null, spawnOptions);
  script.stderr.pipe(process.stderr);
  script.stdout.pipe(process.stdout);
  script.on('exit', process.exit.bind(process));
});

Differences from NPM

  1. Does not add in defaults for scripts like npm run-scripts start (use options.defaultScript)
  2. Does not auto add in the current path, set it in options.env (will append if already has a value)
  3. Does not change users for you, use something like suspawn

See

npm help scripts