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

connect-resource-pipeline

v0.3.1

Published

Middleware for Connect to allow resource transformation via streams.

Downloads

37

Readme

connect-resource-pipeline

Build Status

Middleware for Connect to allow resource transformation via streams.

This middleware was written to support development with gulp.js, and is not at all (not even a little bit) intended to be used standalone or in any kind of production capacity. So don't do that.

Instead, do this:

var gulp = require('gulp');
var connect = require('connect');
var pipeline = require('connect-resource-pipeline');
var less = require('gulp-less');

gulp.task('serve', function () {
    var app = connect();
    app.use(pipeline({root: 'public'}, [
        // Define URLs to match and map them to globs (that are automatically concatenated)
        {url: '/all.js', files: ['js/*.js']},
        // Pipe through your favorite gulp plugins!
        {url: '/styles.css', files: ['less/*.less'], pipeline: function (files) {
            return files.pipe(less());
        }}
    ]));
    app.listen(8080);
});

Installation

npm i connect-resource-pipeline --save

API

var middleware = pipeline([options, ] targets)

options

An object which may contain:

  • root

    Type: string

    Will be used to prefix all non-absolute paths in files, or the URL path if files is empty.

targets

An array that defines URLs to be matched and what to return as a response. Each entry is an object comprised of:

  • url

    Type: string|RegExp

    The URL to match. Matched against url.parse(req.url).pathname.

  • cache (optional)

    Type: string|boolean

    Enables caching of pipeline output. Set to true to enable with the URL used as the cache key, or any string to enable with string used as the cache key.

  • files (optional)

    Type: string|string[]

    File paths to match. Uses vinyl-fs under the hood, so globs are allowed. If omitted, the pathname of the request will be used.

  • pipeline (optional)

    Type: function(stream.Readable, Request): stream.Readable

    A function that takes a stream of files as an argument and returns the result stream. The request object is passed as the second argument.

  • DEPRECATED factories (optional)

    An array of factories that produce processors (gulp plugins). The matched files will be piped through each factory's plugin, in order, before being concatenated and sent as a response.

    This functionality has been deprecated in favor of the far more flexible and gulp-like pipeline property.

middleware.clear([cacheKey])

Clear the contents of cacheKey in the internal cache.

Caching

If you want to cache output and retain the ability to clear the cache (for example within a watch), save a reference to the middleware instance you pass to app.use().

var gulp = require('gulp');
var connect = require('connect');
var pipeline = require('connect-resource-pipeline');

gulp.task('serve', function () {
    var middleware = pipeline([
        {url: '/all.js', cache: 'js', files: ['public/js/*.js']}
    ]);

    gulp.watch('public/js/*.js', function () {
        middleware.clear('js');
    });

    var app = connect();
    app.use(middleware);
    app.listen(8080);
});

Connect compatibility

This has been tested with Connect 2.x and 3.x.

Rationale

Sometimes doing neat things with your build makes running a local development server harder. Wouldn't it be nice if you could use the same plugins your build uses as part of a dynamic dev server? Yes, it would.