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-progeny

v0.4.1

Published

Gulp plugin for dependencies building

Downloads

15,711

Readme

gulp-progeny Build Status

A dependency-resolving plugin for Gulp. It grabs all files related to one modification to building system. Make Gulp Fast Again

##Introduction Gulp provides incremental building. However it is agnostic about the dependencies among files. Say, if child.jade depends on parent.jade, then whenever parent changes child should be recompiled as well. Existing gulp plugins do not support this. Or one could fall back on edit-wait-10s-view loop.

gulp-progeny aims to solve this. If parent.jade is edited and passed to gulp-progeny, all files that recursively depends on that file will be collected by progeny and are passed to succesive building stream.

##What does gulp-progeny do This plugin brings the agility of brunch to gulp world. It provides generic dependency detection to various file types. progeny parses files by grepping specific import statements, and builds dependency trees for building tasks. So it just use Regular Expression to extract dependency information. This simple solution is fast and dirty, but also working.

##Usage gulp-progeny out of box supports jade, less, sass and stylus. To exploit the power of gulp-progeny, use gulp-cached in tandem.

var cache = require('gulp-cached');
var progeny = require('gulp-progeny');
var stylus = require('gulp-stylus');

gulp.task('style', function(){
  return gulp.src('*.styl')
    .pipe(cache('style'))
    .pipe(progeny())
    .pipe(stylus())
});

gulp.task('watch', function(){
  gulp.watch('*.styl', ['style']);
});

cached will pass all files to progeny in the first run, which enables dependency tree building, just pass changed files later for incremental building.

Advanced configuration

As gulp-progeny includes progeny in its core, please see their configuration docs for the options that can be used with this plugin.

Limitation

gulp-progeny, by the virtue of its design, has following limitations.

  1. Filenames must be static in source code. Otherwise regexp fails to work.

  2. Sass/Scss filenames should not contain apostrophes. This limitation is due toSass's multiple import feature. Matching filenames with '" is far beyond the reach of regular expressions with only one match, which is the format used in this plug in.

Limitations above are almost ineluctable for this simple plugin. To keep API and extension simple and generic, some features are doomed to be dropped. This plugin does not fill the chasm between a single one Regexp and full-bloom parsers.