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-intelli-watch

v0.4.1

Published

Rebuilds only the endpoints relevant to changed files

Downloads

11

Readme

gulp-intelli-watch

Rebuilds only the endpoints relevant to changed files

Useage

const intelliWatch = require('gulp-intelli-watch');

intelliWatch(glob, taskLogic);

Arguments

  • glob String|Array [required] Pattern to match all endpoints for task.

  • taskLogic(glob) Function [required] Task to run when files are changed

    • glob String|Array A subset of files from the glob passed into intelliWatch

Requirements

To use gulp-intelli-watch, you must follow these rules:

  1. Your task logic must return a stream.
  2. Your task needs to take an argument that receives your typical gulp src glob.
  3. If you are using a language that bundles multiple files into a single endpoint, you need to initialize source maps in your build process.

Helpful Tips

We need to tie into your stream to analyze the files to watch, so you must return a stream.

This means:

  • You cannot omit a return value.
  • You cannot return something else such as a Promise (soon to come, hopefully)

If you are used to writing your task in the following pattern:

function styles() {
    gulp.src(config.styles.src)
        .pipe(sass())
        .pipe(gulp.dest(config.styles.dest));
}

gulp.task('styles', styles);

gulp.task('styles:watch', () => {
    gulp.watch(config.styles.src, styles);
});

You will need to refactor your task logic as follows:

function stylesTaskLogic(src) {
    return gulp.src(src)
        .pipe(sourcemaps.init())
        .pipe(sass())
        .pipe(gulp.dest(config.styles.dest));
}

function styles() {
    stylesTaskLogic(config.styles.src);
}

gulp.task('styles', styles);

gulp.task('styles:watch', intelliWatch(config.styles.src, stylesTaskLogic));

Note we are returning the gulp.src inside the stylesTaskLogic.


Be sure to include gulp-sourcemaps where applicable. You do not have to write the sourcemaps if you do not want to, but you need to at least pipe init in your stream before returning.

function stylesTaskLogic(src) {
    return gulp.src(src)
        .pipe(sourcemaps.init())
        // ^ we need this!!
        .pipe(sass())
        .pipe(gulp.dest(config.styles.dest));
}