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

spawt

v0.1.0

Published

Spawn commands in a cross platform manner. Good spawt!

Downloads

8

Readme

Spawt

spawt('npm run x') instead of spawn(npm.cmd, ['run', 'x'])

Quick Start

npm install spawt
var run = require('spawt')

run('npm run build')

Background

In the Node world there are two key ways to run child processes spawn or exec.

One is more convenient (exec) while one doesn't overflow your buffer, and protects you from command injections.

spawt gives you a convenient exec like API but uses spawn under the hood. It also will try some common (and customizable) file extensions to try if the initial file can't be found on your path.

spawt also returns the underlying child_process object, so you can listen to error and message events as if you want to do it manually.

spawt will add the extension .cmd on windows automatically, and use no extension on any other os. This is inline with npm's standard bin generation feature.

API

spawt(command: String, options: {})

  • command The command to run (e.g. npm run whatever)
  • options Options to pass to the underlying child_process object

Returns child_process

Launches a new process with the given command.

The second argument is used to specify additional options, with these defaults:

{ cwd: undefined,
  env: process.env
}

Use cwd to specify the working directory from which the process is spawned. If not given, the default is to inherit the current working directory.

Use env to specify environment variables that will be visible to the new process, the default is process.env.

And we're done!