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

exstatic

v0.3.2

Published

Express middleware to help with the bundling, minifying, obfuscating and versioning of static assets for delivery over a CDN.

Downloads

17

Readme

exstatic

Connect/Express-style middleware to help with the bundling, minifying, obfuscating and versioning of static assets for delivery over a CDN.

Installation

$ npm install exstatic

Quick Start

var
express = require('express'),
exstatic = require('exstatic'),
staticAssets = exstatic(),
app = express();

staticAssets.createAssetsFromDirectory(
    '/static/:version/:dirname/:basename.:cacheId:extname',
    __dirname + '/public'
    );

app.use(staticAssets.middleware);

app.listen(80);

A directory structure like this:

app
 +- public
 |   +- css
 |   |   +- style.css
 |   +- js
 |       +- jquery.js
 |       +- app.js
 +- app.js

will generate asset URLs similar to the following:

GET /static/1359528874/css/style.d9b28cb1.css
GET /static/1359528874/js/jquery.83f534af.js
GET /static/1359528874/js/app.057d0df0.js

Usage

Startup options

exstatic can be started with some options to help structure generated URLs.

  • host: The host to prefix any generated URLs with.
  • cachePath: The path to store rendered file output.
  • version: A version string that may be used in the generated URLs.
  • noCleanup: Don't delete the files stored in the cache path when the application exits.
  • typeSearchPath: A string or an array of strings of paths that should be searched to find asset type libraries.
var exstatic = require('exstatic')
    staticAssets = exstatic({
                        host: 'http://example.com',
                        cachePath: __dirname + '/static_cache',
                        version: 'v1'
                    });

Specifying Assets

createAssetsFromDirectory(pattern, directory)

Creates versioned asset URLs from the contents of one or more directories.

Arguments

  • pattern: A pattern string to build the asset URLs. Variables in the pattern are preceded by a colon, just like path parameters in Express routing. The available variables are:

    • :path: The path of the asset relative to the directory argument from which is was found, stripped of all preceding ../, if any.
    • :dirname: The directory component of :path.
    • :basename: The filename component of :path, without the extension.
    • :extname: The file extension component of :path.
    • :version: The version string specified in the startup options (defaults to a unix timestamp of when exstatic is required).
    • :cacheId: A truncated MD5 hash of the file contents.
  • directory: A string or array of strings of directories of files to be served.

Example

staticAssets.createAssetsFromDirectory(
    '/static/:version/:dirname/:cacheId/:basename:extname',
    [
        './public/foo',
        './public/bar'
    ]
);

createAsset(type, settings)

Creates a single asset to be served with the specified settings.

Arguments

  • type: The preprocessing/compression strategy to use on this collection of files.

  • settings: An object containing the following parameters:

    • id (required): A string identifier for this asset.

    • pattern (required): A pattern string to build the asset URL. Variables in the pattern are preceded by a colon, just like path parameters in Express routing. The available variables are:

      • :version: The version string specified in the startup options (defaults to a unix timestamp of when exstatic is required).
      • :cacheId: A truncated MD5 hash of the file contents.
    • files (required): An array of strings of file paths to be preprocessed and/or compressed per the type argument, and be concatenated into a single file.

    • preprocess: An optional function to allow further preprocessing of a file, after any normal preprocessing done by that type, before being compressed and concatenated with the other members of the files array. The function receives three arguments: the path of the current file, the contents of the current file (a string if a text file, a buffer if binary), and a callback. The callback should be invoked when the work of the function is complete. The callback accepts two arguments: an error object (null if no error occurred) and the result of the processing of the file contents.

Example

staticAssets.createAsset(
    'javascript',
    {
        id: 'js/lib.js',
        pattern: '/static/:version/js/:cacheId/lib.js',
        files: [
            './public/lib/js/underscore.js',
            './public/lib/js/jquery.js',
            './public/lib/js/jquery.form2json.js',
            './public/lib/js/jquery.locus.js',
            './public/lib/js/backbone.js'
        ]
    }
);

middleware

In order to start serving the defined assets and reference their generated URLs from your templates, the exstatic middleware method must be used by your Express application:

var
express = require('express'),
exstatic = require('exstatic')
staticAssets = exstatic(),
app = express();

// assets get defined here
// express configuration gets started here

app.use(staticAssets.middleware);

app.listen(80);

Referencing the assets from templates

N.B.: Currently, exstatic only provides a means for referencing assets for Mustache-style languages like Hogan.js and handlebars.js. (I'll gladly accept patches to extend support!)

To render the CDN-friendly asset URL from the asset defined in the above createAsset example, just use the {{#staticAssets}} lambda:

<!DOCTYPE html>
<html>
    <head>
        <title>exstatic!</title>

        <script type="text/javascript" src="{{#staticAssets}}js/lib.js{{/staticAssets}}></script>
    </head>
    <body>
    </body>
</html>

Asset Types

When creating assets using createAsset, a type must be specified as the first argument. The following types are currently available:

Built-in

  • javascript: The javascript type uses UglifyJS to obfuscate and compress the supplied files before concatenating them into a single asset.
  • stylus: The stylus type uses Stylus to generate CSS from -- what else -- stylus files before compressing and concatenating them into a single asset.
  • png: The png type can only handle a single PNG image in it's files array. It will run optipng using node-optipng on the file and serve the compressed version.

Additional Types

Additional types can be created simply by inheriting the Asset object defined in lib/Asset.js. The built-in types (in lib/assets/) can help in getting started.

To use your own types, make sure the folder they're kept in is included in the typeSearchPath setting initially passed to exstatic.

Examples

Examples are available with the git repository. Each requires Express v3.x, and should be run from within it's own directory.

Assuming express is installed and accessible from where git clone is run:

$ git clone [email protected]:2sidedfigure/exstatic.git
$ cd exstatic/examples/js
$ node index.js

Author

± ryan ([email protected]). Development was and continues to be sponsored by YellowBot.

License

Copyright (c) 2013 Ryan Ettipio

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.