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

asparagus

v0.2.1

Published

Flexible template compiler. Compile all or some of your templates, even those in parallel sub-folders, to a location that may or may not yet exist.

Downloads

9

Readme

asparagus

Prefer your veg in some colour? asparagus pages

Template compile tool for NodeJS. Compile all or some of your templates, even those in parallel sub-folders, to a location that may or may not yet exist.

Build Status NPM version

Install globally to use the binary commmands

$ npm install asparagus -g

adds a binary to the path so you can run asparagus from the command line

Command line

$ asparagus /path/to/source/folder namespace=mytemplates format=camelcase

JavaScript

var asparagus = require('asparagus');

// A source parameter is required as the first argument to asparagus

asparagus(__dirname + '/views', {
    dest: __dirname + '/public/templates',
    format: 'camelcase',
    namespace: 'partials',
    basedir: __dirname + '/views/dev',
    exclusive: 'includes'
});

Plays nice with Gulp too simply wrap the above in a gulp task, I.e.,

var gulp = require('gulp'),
    asparagus = require('asparagus');

gulp.task('asparagus', function () {
    asparagus(__dirname + '/views', {
        dest: __dirname + '/public/templates',
        format: 'camelcase',
        namespace: 'partials',
        basedir: __dirname + '/views/dev',
        exclusive: 'includes'
});

Browser

Templates are added to the namespace by the function name corresponding to their filename. If you are using Jade, you'll need to include Jade Runtime in the browser.

window.partials = {
    functionName: function () { ..... }
};

Options

[dest] {String}
    - The final intended destination of the compiled templates(s), defaults to the value of the source parameter.

[format] {String}
    - The format of each compiled template function name in the namespace, defaults to 'underscore' delimited function names.

[namespace] {String}
    - The namespace object on the `window` object that will store references to the compiled template functions, defaults to 'templates'.

[basedir] {String}
    - allows for absolute include paths, defaults to the value of the source parameter.

[exclusive] {String}
    - When set to an existing directory name in the source path, compiles files only from and to that directory name within source and dest paths.

Explained

The following example will compile all and only, the files in the folder named 'includes' within the path; __dirname + 'views/source'.

The compiled functions will be assigned to a hash called 'partials' and attached to the window object.

Each compiled template function within window.partials will be identifiable by an id created from its original filename and formatted as per the format option, which in this case is 'camelcase'

So this;

views/
    dev/
        includes/
            my-tmpl.jade
    en/
        includes/
            my-tmpl.jade

Outputs;

public/
    templates/
        dev/
            includes/
                my-tmpl.js
        en/
            includes/
                my-tmpl.js

And when one is loaded

<script src='templates/en/includes/my-tmpl.js'></script>

Gives you

window.partials = {
    myTmpl: function () { ..... }
};

Any absolute include statements within any of the original templates will be appended to the basedir option, __dirname + '/views/dev'.