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

gulp-cause

v0.0.8

Published

declarative gulp tasks causality

Downloads

91

Readme

gulp-cause

version npm dependencies build status js-standard-style

Declarative gulp tasks composition and watching causality. Better with beverage.

Use

NPM

Work in Progress

Some of the functionality described below isn't implemented yet. See the trailing comments in the example about which parts that is.

Here is an example of how this would work:

var gulp = require('gulp');
// create task, two, three, more
require('gulp-cause')(gulp, [
  'alias', 'task',
  'both', {parallel: ['two', 'three']}, // not implemented yet
  'sequence', {series: ['both', 'more']}, // not implemented yet
  'task', ['src/*'], // shorthand, works fine in most cases (where watch is needed)
  'two', [['src/*'], fn], // this array is gulp-watch args
  'cool', {tasks: ['more'], watch: ['place/*']} // not implemented yet
]);

The code above instructs gulp-cause to:

  1. make alias of an existing task
  2. create task both to run tasks two and three in parallel
  3. create task sequence to first run task both (declared above), then task more
  4. task:watch will be created - any src/* changes will cause task to be run
  5. two:watch uses gulp-watch rather than gulp.watch - documented further down
  6. task cool watches place/* files and can have any name, not just more:watch

Rationale

There must be an even number of causality pairs in the array. Having two items per line is good for readability. The left one is always a task name to either be created or invoked - depending on the right-hand-side. The data is processed one pair of items at a time, thus with each step one can depend on tasks from the previous steps. If no tasks existed to begin with, then gulp-cause couldn't do a thing.

Watch

Using gulp.watch by default, unless the watch value is more complex than an array of globs to watch. In such a case, gulp-cause will interpret the array as a gulp-watch arguments list to be applied. See gulp-npm-test for example. Which of the two is preferable depends on the use case.

Test Build Status

npm test

Develop Dependency Status devDependency Status

js-standard-style

License

MIT