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

require-tasks

v1.1.0

Published

A tool to load tasks (from a directory) and output contents as a mapped object

Downloads

421

Readme

require-tasks

Build Status Build Status David

A tool to require a directory, and (optionally) inject each file in that directory with supplied arguments.

For example, given the following directory structure:

├── build
   ├── tasks
      └── copy.js
      └── webpack.js

this tool (when configured to search in build/tasks) will load each file in tasks, and will inject each task with supplied arguments, and then return a structure like:

{
  copy() {}, // reference to what copy.js returns
  webpack() {} // reference to what webpack.js returns
}

Install

npm i require-tasks -D

Usage

import requireTasks from 'require-tasks';

const tasks = requireTasks(['build/tasks'])(); // any arguments passed will be made available to any task that exports a function

tasks will be an object with each key representing the filename of every file in build/tasks. Additionally, any files that export an object (or a function that returns an object) will available as a property on the filename as the key.

Multi-tasks

Additionally, if a task returns an object, that task will be treated as "multi-task" and each key in the object will be added to the parent task. For example, given the following task:

build/tasks/copy.js

export default function copy(...args) {
  return {
    benz() {
      // do something
    },
    otherBenz() {
      // do something else
    },
    otherOtherBenz() {
      // do this thing
    }
  };
}

The returned object will contain a property like so:

{
  copy: {
    benz() {},
    otherBenz() {},
    otherOtherBenz() {}
  }
}