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 🙏

© 2026 – Pkg Stats / Ryan Hefner

netsells-gulp

v0.12.0

Published

Netsells custom gulp file

Downloads

57

Readme

Gulp

Netsells custom gulp file. This module is intended to speed up development by making tasks consistent, as well as providing documentation and source control as improvements are made.

If working on multiple projects using the this gulpfile, I would recommend installing this module globally (npm install -g netsells-gulp) so that you don't need to install all the dependencies in each project.

More tasks will be added eventually, as well as improvements in performance.

Setup

The gulpfile itself needs only be the following:

var gulp = require('gulp');

gulp.tasks = require('netsells-gulp')({
    config: require('./gulp.config')
});

You can specify the default component to compile, or you can specify the --c=<component> flag after the gulp command. This works for any specific gulp too, e.g. gulp less, gulp watch, etc.

The gulp watch command also accepts a --build flag which will run the default task specified in your config.

This module will handle the rest, as long as you provide a valid config for it to read.

Config

Config should be provided in the form of a gulp.config.js file in the same directory as your gulpfile. The basic config format is as follows:

var path = require('gulp-paths');

module.exports = {
    component: {
        task: {
            before: ['Array of tasks to perform before this one'],
            watch: {
                src: 'Array or string of files to watch',
                task: 'Task to execute when changes are made'
            },
            src: [
            	'Array of files to pass into the pipe'
            ],
            dest: 'Path to move files to'
        }
    }
}

In context:

var path = require('gulp-paths');

module.exports = {
    global: {
        install: {
            watch: ['./bower.json', './package.json'],
            src: ['./bower.json', './package.json']
        }
    },
    app: {
        default: {
            before: ['javascript', 'less']
        },
        coffee: {
            watch: {
                src: path.asset('app/coffee/**/**'),
                task: ['javascript']
            },
            src: [
                ...
                path.asset('app/coffee/app.coffee'),
            ],
            dest: path.asset('app/js')
        },
        less: {
            ...
        },
        images: {
            ...
        },
        javascript: {
            before: ['templates', 'coffee'],
            src: [
                path.bower('jquery/dist/jquery.js'),
                // Place additional bower dependencies here in the format used above
                path.asset('app/js/templates.js'),
                path.asset('app/js/app.js')
            ],
            dest: path.js('app')
        },
        templates: {
            ...
        },
    },
    frontend: {
        default: {
            before: ['javascript', 'less']
        },
        less: {
            ...
        },
        images: {
            ...
        },
        ...
    },
}

Tasks

  • Install
    • Bower install and npm install
  • CoffeeScript
    • Concats all coffeescript files into a single file
    • Compiles to Javascript
    • Moves to the JavaScript staging folder
  • JST Templates
    • .html templates that use the lodash/underscore templating syntax
    • Compiles to JavaScript
    • Moves to the JavaScript staging folder
  • JSX
    • Compiles JSX files to javascript
    • Moves to the JavaScript staging folder
  • JavaScript
    • Concats all JavaScript files including those in the staging area (if specified in config)
    • Moved to the public folder
    • A Minified version is created
    • Moved to the public folder also
  • LESS
    • Compiles to CSS
    • Auto-prefixes any vendor specific attributes
    • Moved to the public folder
    • Minified
    • Moved to the public folder
    • Split up into multiple files if IE selector limit is reached
  • SASS
    • Compiles to CSS
    • Auto-prefixes any vendor specific attributes
    • Moved to the public folder
    • Minified
    • Moved to thje public folder
    • Split up into multiple files if IE selector limit is reached
  • Images
    • Images are compressed
    • Moved to the public folder

Vendor tasks

Need to compile certain files but don't want these compiled into a single bloated file with your app logic especially if they're not going to change often (mainly package manager dependencies such as bower)? Well no problem! Simply name the task in the following format: vendor:javascript for example, and a separate file will be compiled named vendor.javascript.js on compile. This also speeds up compiling on save immensely - Craig will be happy!

To-do

Functionality

  • ~~Require dependencies on a per task basis, rather than all at once through the $ prefix~~
  • Prompt for component
  • Overridable tasks
  • Better error catching
  • Gutils functionality
  • Cleanup of compiled assets before running
  • ~~Vendor tasks~~

Tasks

  • PHPUnit
  • Codecept
  • ~~SASS/SCSS~~