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

atlas-interactive-shell

v1.0.2

Published

Runs a shell command interactively, abstracts useful callbacks as opposed to manually listening for events.

Downloads

4

Readme

atlas-interactive-shell

Runs a shell command interactively, abstracts useful callbacks as opposed to manually listening for events.

Travis


install

npm install --save atlas-interactive-shell

why

Sometimes you need to run a command and programmatically interact with the standard input when prompted with a message. The implementation looks something like this:

const { spawn } = require("child_process");
const child = spawn(cmd);
const onDone = (err, code) => {
  // only run this once
}
child.stdout.on("data", data => {
  // maybe write to stdin
})
child.stderr.on("data", data => {
  // maybe write to stdin or kill
})
child.on("exit", code => {
  // call onDone if we haven't already
})
child.on("close", code => {
  // call onDone if we haven't already
})
child.on("error", err => {
  // call onDone with error if we haven't already
})

I would rather keep a clean house and not litter my codebase with this event and stream stuff. So, I tried to come up with a decent API to abstract it away.

examples

passing command and opts

The first argument is a command, the second argument is spawn opts and is entirely optional.

const Shell = require("atlas-interactive-shell");
const cmd = "ls && mkdir -p new-dir/new-sub-dir && ls new-dir";
const opts = {cwd: __dirname, ...otherSpawnOpts};
const shell = new Shell(cmd, opts);

onDone callback

This is called only once, whether the command exits normally or with an error:

...
shell.onDone((err, code) => {
  if (!err) console.log(code)
})

onData callback

Captures stderr and stdout, allowing you to reply with an error or a message, respectively:

...
shell.onData((stderr, stdout, reply) => {
  if (stderr) 
    return reply(new Error("oops!")); // triggers onDone with our err
  if (stdout === "enter username:")
    return reply("atlassubbed\n");
})

logging

The spawned command will not log anything unless you call the log method, in which case all stderr and stdout will be piped to the parent process:

...
shell.log()

chaining everything

All of the methods can be chained, since they just return the instance:

...
shell.log().onDone(err => console.error(err)).onData(stderr => {
  stderr && console.log(stderr)
})

caveats

Don't pass unsanitized user input into this function.