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

gonk

v0.1.2

Published

A script runner that sits on your path

Downloads

7

Readme

gonk

Easily run your Node.js scripts from anywhere without cluttering your path.

Build Status

Installation

You can install Gonk using NPM

npm install -g gonk

Usage

Gonk is a script runner. User scripts are kept in the .gonk-scripts directory in the $HOME directory of the logged in user. You can execute a script in that directory like so:

$ gonk print-name-of-script.js
Name of Script!
$

The ".js" of the script name is optional. Scripts passed without an extension are assumed to be Node.js scripts. Currently, only Node.js scripts are supported. This will soon change is adding support for more is pretty trivial.

Any arguments specified after the name of the script are passed to the script. e.g.

$ gonk print-first-argument.js first-argument
first-argument!
$

Configuration

Currently, the only configurable aspect of Gonk is the scripts directory. The scripts directory is read from the GONK_SCRIPTS_DIRECTORY environment variable.

Why?

All I basically wanted to get out of this is the ability to run scripts that sit in a directory from anywhere on my machine, without cluttering the PATH with all of them.

I'm also planning to perhaps add some library functions that most scripts run with Gonk would want to use. Not sure about it though, I don't want the project to turn into some generic util.* bloated nightmare function bucket.