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

owlister

v1.2.0

Published

Maintainable terminal commands.

Downloads

16

Readme

(( '^' )) Owlister v.1.0.0

$ npm install -g owlister Instructions for use at bottom of readme.

Owlister provides a prettier way to manage terminal commands and Node.js tasks.

// root/tasks.owl

var stylus-in = ./styl;
var stylus-out = ./css;
var pug-in = ./index.pug;
var pug-out = ./index.html;
var babel-in = ./babel;
var babel-out = ./js;

var watch-stylus = stylus -w (stylus-in) -o (stylus-out);
var live-server:stylus-watch => '(watch-stylus)' 'live-server';
var watch-pug = pug -w (pug-in) > (pug-out);
var watch-babel = babel (babel-in) -w --out-dir (babel-out);

var build => '(watch-stylus)'
             '(watch-pug)'
             '(watch-babel)'
             'live-server';

Format how you like.

There is no restriction on how you organize your Owlister scripts. You can have a huge script all on one line or split into 97 lines with one word on each. The rules for defining tasks are as follows:

  • Begin your task declaration with the var keyword.
  • Use only alphanumerical characters and : or - in your tasknames.
  • End each task, not each line, with a semicolon.
  • After declaring a task, refer to it using its name in parenthesis. (task-name)
  • For concurrent tasks (multiple commands at once), use the fat arrow. =>

Variable Support

Variables in Owlister are simple and attractive. After a variable is set, calling that variable in another task is as easy as (variable).

Concurrent Tasks

When declaring a task that performs multiple tasks at the same time, use the fat arrow => instead of the standard equal sign =. Owlister has but one single dependency, and that is Concurrently. The fat arrow signifies that Concurrently is needed for this task and that the separated commands inside this task should be run side by side. Be sure to encompass each individual command in quotes if using concurrency.

var my-task:Rocks1 => 'task one' 'task two' 'task three';

How to use Owlister

  1. $ npm install -g owlister
  2. Create a tasks.owl file in your root directory.
  3. Create your tasks in your tasks.owl file.
  4. $ owl taskName

TODO

  • Integrate owl cli-help <cli tool> to assist users in creating scripts with various CLI tools.