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

superintendent

v0.0.1

Published

superintendent ==============

Downloads

7

Readme

superintendent

Introduction

Orchestrating tasks expressed as functions - playing with ideas for the future Gulp task system. The idea here is to experiment with tasks-as-functions idea expressed here: https://github.com/gulpjs/gulp/issues/355#issuecomment-45052782

In a nutshell we would like to have task dependencies expressed as (asynchronous) functions, instead of tasks as of today. It would make it possible to covert today's code:

gulp.task('foo', function(done) {
    //do something foo-lish here
    done();
});

gulp.task('bar', function(done) {
    //do something bar-ish here
    done();
});

gulp.task('default', ['foo', 'bar'], function(done) {
    // do something when 'foo' and 'bar' are done
});

into:

function foo(done) {
    //do something foo-lish here
    done();
}

function bar(done) {
    //do something bar-ish here
    done();
};

gulp.task('default', gulp.parallel(foo, bar) , function(done) {
    // do something when 'foo' and 'bar' are done
});

or, if you prefer to have foo and bar being executed in a sequence:

gulp.task('default', gulp.series(foo, bar) , function(done) {
    // do something when 'foo' and 'bar' are done
});

Obviously one should be able to combine the parallel and series calls, ex.:

gulp.task('default', gulp.series(foo, gulp.parallel(bar, baz) , function(done) {
    // do something when 'foo' and 'bar' and 'baz' are done
});

Such approach has several advantages over the current system:

  • it is possible to precisely control order of execution of dependent tasks
  • a set of dependent tasks to be executed could be built dynamically
  • using function dependencies instead of tasks make it possible to define / expose only tasks that make sense for the users; in a way those functions can act as "private tasks".

Spec

A discussion about a new task system for Gulp4 is scattered over several GitHub repositories and issues. I would love to centralise this discussion and open it up to the community for discussion.

Different ways of specifying dependencies

  • gulp.task('default', [], function() {})) - should work as of today
  • gulp.task('default', ['foo', 'bar'], function() {})) - where foo and bar are tasks should work as of today
  • gulp.task('default', gulp.parallel('foo', 'bar'), function() {})) - where foo and bar are tasks should be equivalent to the above
  • gulp.task('default', gulp.parallel(foo, bar), function() {})) - where foo and bar are function references
  • gulp.task('default', gulp.series(foo, bar), function() {})) - where foo and bar are function references

Asynchronous functions that can be combined

The gulp.parallel and gulp.series arguments should accept any asynchronous functions. The end-of-processing for a given function can be expressed be:

  • synchronously returning a value / throwing an exception
  • invoking a provided callback
  • returning a promise
  • returning a stream
  • it would be really easy to extend it to other node-async processing patterns (process, http request etc.)

Implementation

This repo contains a minimal, non-production ready implementation of a promise-based functions dependency system that could potentially replace the current task orchestration system.

There is a separate repository containing a POC for a minimal gulp implementation based on this function orchestration.