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 🙏

© 2025 – Pkg Stats / Ryan Hefner

gulp-nittro

v0.2.2

Published

Nittro builder Gulp plugin

Downloads

16

Readme

gulp-nittro

Nittro builder plugin for Gulp

Installation

npm install --save-dev gulp-nittro

Usage

Shared builder

This has the benefit of only building the internal dependency tree once, but it's not that big of a deal anyway..

var gulp = require('gulp'),
    nittro = require('gulp-nittro');
    
var builder = new nittro.Builder({
    // (options)
});

gulp.task('js', function() {
    return nittro('js', builder)
        .pipe(/* ... */);
});

gulp.task('css', function() {
    return nittro('css', builder)
        .pipe(/* ... */);
});

Separate builder

Alternatively, you can pass the options object directly to the plugin; the options object will then internally be converted to a Builder instance anyway, so this may just be a nicer way of writing things when your options between tasks vary wildly.

var gulp = require('gulp'),
    nittro = require('gulp-nittro');
    
gulp.task('js', function() {
    return nittro('js', { /* (options) */ })
        .pipe(/* ... */);
});

gulp.task('css', function() {
    return nittro('css', { /* (options) */ })
        .pipe(/* ... */);
});

Options

var options = {
    vendor: {
        js: [
            // libraries from other vendors, such as jQuery...
        ],
        css: [
            // ... or Twitter Bootstrap etc.
        ]
    },
    
    // Nittro components to include. Note that dependencies are
    // added automatically, so if you ask for e.g. the "page"
    // component, the "core" and "ajax" packages will be added
    // automatically.
    base: {
        core: true,
        datetime: true,
        neon: true,
        di: true,
        ajax: true,
        forms: true, // note that including the forms component
            // will automatically include the netteForms.js asset
        page: true,
        flashes: true,
        routing: true
    },
    extras: {
        checklist: true,
        dialogs: true,
        confirm: true,
        dropzone: true,
        paginator: true,
        keymap: true,
        storage: true
    },
    
    // other libraries to include after Nittro, e.g. your site's
    // proprietary libraries and styles
    libraries: {
        js: [
        
        ],
        css: [
        
        ]
    },
    bootstrap: true, // true or object = generated bootstrap, otherwise
                    // provide a path to your custom bootstrap script
    stack: true // include the _stack library
}