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

rrun

v1.0.5

Published

Require and run a js file with one command

Downloads

5

Readme

rrun

This is a small utility to require and run modules from the command line.

Install

npm i -D rrun

Usage

Command Line:

$ rrun path/to/some-module [arguments ...]

rrun will require a file and run it's default export with any arguments passed along. It can be useful for running development tasks. This way, tasks can be run directly from npm scripts or the command line, but they can also be required and run from other task files. It's not intended to run anything other than basic node modules that export a single function.

Example Task Setup:

Assume we have a task to compile sass and we want to run it from npm scripts and also from our watch task.

// sass-task.js

module.exports = () => {
  // do sassy stuff
};

You can use it in your watch task:

const chokidar = require('chokidar');
const sass = require('path/to/sass-task');

chokidar.watch('./src/scss/**/*.scss').on('change', sass);

And you can rrun it from your npm scripts:

"scripts": {
  "sass": "rrun path/to/sass-task"
}

PSA: You can do the same thing without using rrun:

"scripts": {
  "any-task": "node -e \"require('path/to/module')()\""
}

But ☝️ that is kind of ugly and co-workers may find it confusing.