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 🙏

© 2026 – Pkg Stats / Ryan Hefner

oh-my-terminal

v1.1.2

Published

Terminal interface for NodeJS

Downloads

122

Readme

oh-my-terminal

Last version Build Status Dependency status Dev Dependencies Status NPM Status Donate

Simple and unmistakable terminal interface for NodeJS.

Why

  • Based in NodeJS exec and spawn native interface.
  • Automatically provide a polyfill for non native compatible node versions (for example, execSync under 0.10).
  • Uniform methods for synchronously and asynchronously, just decide providing or not a callback.
  • Little improvements, like posibility for run a set of commands in the same command or more information about the process status in sync versions.

Install

npm install oh-my-terminal --save

Example

First load the library:

var terminal = require('oh-my-terminal');

Simple Usage

Now, you can run a command using exec or spawn methods. Exists slight difference between us (as you know from child_process.

Using exec:

var term = terminal.exec('echo hello world');

console.log(term);
// => {
//   stdout: 'hello world\n',
//   stderr: '',
//   status: 0
// }

Using spawn:

var term = terminal.exec('echo hello world');

console.log(term);
// => {
//   pid: 95109,
//   output: [ null, 'hello world\n', '' ],
//   stdout: 'hello world\n',
//   stderr: '',
//   status: 0,
//   signal: null
// }

Custom Options

Like exec or spawn, you can provide a custom options for the command:

var options = {
  timeout: 1000
};
var term = terminal.exec('echo hello world', options);

console.log(term.stdout);
// => 'hello world\n'

More than one

If you need to run one command, maybe you need to run more than one. Just instead of string pass an array of command (with or without callback for user synchronously or asynchronously behavior):

terminal.exec(['echo hello', 'echo world'], function(err, commands) {
  console.log(commands[0].stdout);
  // => 'hello world\n'
  console.log(commands[1].stdout);
  // => 'hello world\n'
});

Async mode

Just providing a standard NodeJS callback you activate the async mode for the command:

terminal.exec('echo hello world', function(err, command) {
  console.log(command.stdout);
  // => 'hello world\n'
});

You can run a set of command in async mode as well:

terminal.exec(['echo hello world', 'echo hello world'], function(err, commands) {
  console.log(commands[0].stdout);
  // => 'hello world\n'
  console.log(commands[1].stdout);
  // => 'hello world\n'
});

API

.exec(<command[s]>, [options], [callback])

Invoke child_process.exec (or execSync if you don't provide a callback) function. You can provide just one String command or an Array of command to be executed.

Options are child_process.exec options. { encoding: 'utf8' } by default.

.spawn(<command[s]>, [options], [callback])

Invoke child_process.spawn (or spawnSunc if you don't provide a callback) function. You can provide just one String command or an Array of command to be executed.

Options are child_process.spawn options. { encoding: 'utf8' } by default.

Note that in this case the response is a Stream Object that starts sending back data from the child process in a stream as soon as the child process starts executing.

License

MIT © Kiko Beats