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

load-tasks

v0.1.0-rc.0

Published

A tool to load tasks/files based on a glob pattern, and output file contents as an object

Downloads

10

Readme

load-tasks

A plugin to output a file/task object based on a passed in folder/array of folders.

Usage

The examples below show the usage within gulp, but should work with grunt or any other build system (or even outside of a build system!)

Given the following directory structure:

├── build
   ├── tasks
      └── sass.js
      └── watch.js
      └── webpack.js
└── gulpfile.babel.js

gulpfile.babel.js

import gulp from 'gulp';

import LoadTasks from 'load-tasks';
import { argv } from 'yargs';
import pkg from './package.json';

const tasks = new LoadTasks('./build/tasks')(gulp, {
  args: argv,
  pkg
});

gulp.task('sass', tasks.sass);
gulp.task('watch', tasks.watch);
gulp.task('webpack', tasks.webpack);

gulp.task('default', ['sass', 'webpack', 'watch']));

Note that any arguments passed to the closure (2nd function call) are passed to the imported tasks/files, if any tasks/files export a function!

build/tasks/sass.js

'use strict';
import sass from 'gulp-sass';

// note that both es6 and commonjs exports can be used, but es6 exports need to export `default`
export default (gulp, config) => {
  return () => {
    return gulp.src('src/**/*.scss')
      .pipe(sass().on('error', sass.logError))
      .pipe(gulp.dest('dist'));
  };
};

const tasks is now an object populated with the exported contents of each of the tasks, e.g.

{
 sass() {
  // the gulp sass function we defined above!
 },
 watch() {
  // whatever `watch.js` exports!
 },
 webpack() {
  // whatever `webpack.js` exports!
 }
}