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

async-exec

v1.1.0

Published

Promise based exec

Downloads

2,098

Readme

Async-Exec

TypeScript

Have you ever wanted to exec things asyncly? Now you can!

Usage

npm install -S async-exec

Then in your code use any of the following patterns:

Default

The default export is intended to be pretty convenient.

import exec from 'async-exec';

exec(command: string, log: boolean)

Run a single command expressed as a string and return the stdout when complete.

await exec(`osascript -e "set volume ${scaledVolume}"`);
const tsFiles = await exec(`find . -name "*.ts"`);

For tee-style logging, where the output is both sent to stdout as it arrives, and captured in the return value, set the second argument to true.

exec('ls', true);

Other Exports

These other functions are provided in case they are useful.

execAndLog(command: string)

In addition to returning the stdout, this function will console.log each line.

execWithCallbackOnLine(command: string, funcForLine: (line: string) => any)

Run a command, return the stdout and call a function for each line of output. You could use this to console.log only the lines you want.

execWithCallbackOnData(command: string, funcForData: ((data: Object) => any) = null)

Run a command, return stdout and call a function on every 'data' event. This function gives you access to the raw data which you can parse any way you'd like for your situation.

Contributing

Go ahead and send me PRs. I love them. Especially if they contain tests and don't check in generated files.

Not sure how to fix it yourself? Submit an issue and we'll get it done eventually!

Publishing

Mostly for my own recollection, publishing goes like this.

<commit changes>
npm version <major|minor|patch>
git push origin master
npm publish