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

advk

v0.1.0

Published

Lightweight abstraction for executing task runners like Grunt, Gulp, etc.

Downloads

9

Readme

Aardvark (advk)

Lightweight abstraction for executing task runners like Grunt, Gulp, etc.

Install

Install the advk CLI globally:

$ npm install -g advk

Usage

Create a .advk.json file in your project directory (or one of its ancestors) to tell Aardvark where to find your task runner and how to execute it.

{
    "taskRunnerDir": "path/to/gruntjs",
    "taskRunnerBin": "grunt",
    "workingDirArg": "--cwd"
}
  • taskRunnerDir - path to the task runner. This is where your Gruntfile.js, gulpfile.js, etc lives; at the very least should contain a package.json. Aardvark will perform an npm install in this directory if necessary.
  • taskRunnerBin - the name of the bin file for the task runner e.g. grunt, gulp, etc.
  • workingDirArg - name of the commandline arg to specify the working directory to run the tasks on (i.e. the directory you ran advk from)

Execute advk in the directory you want to run tasks on, all arguments are passed through to the relevant task runner.

$ advk build test

For example, given the .advk.json file above (in the ~/Projects dir) and running advk build test in ~/Projects/example will result in Aardvark performing roughly the following operations:

$ cd ~/Projects/path/to/gruntjs
$ npm install
$ node_modules/.bin/grunt --cwd ~/Projects/example build test

License

Copyright (c) 2014 Orion Health MIT License (enclosed)