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

grunt-dust-html-signate

v1.0.1

Published

Grunt task to render Dust templates to HTML

Downloads

8

Readme

About

This task renders Dust templates against a context to produce HTML.

Getting Started

Install this plugin with the command:

npm install grunt-dust-html

Next, add this line to your project's grunt file:

grunt.loadNpmTasks("grunt-dust-html");

Lastly, add the configuration settings (see below) to your grunt file.

Documentation

This task has two required properties, src and dest. src is the path to your source file and dest is the file this task will write to (relative to the grunt.js file). If this file already exists it will be overwritten.

An example configuration looks like this:

grunt.initConfig({
  dusthtml: {
    dist: {
      src: "src/home.dust",
      dest: "dist/home.html",

      options: {
        // see below for options. this is optional.
      }
    }
  }
});

Optional Configuration Properties

This plugin can be customized by specifying the following options:

  • whitespace (Boolean): Whether or not to preserve whitespace. false by default.
  • partialsDir (String|Array): Path to one or more directories that contain your partials.
  • defaultExt (String): The default template extension of your partials. Defaults to .dust.
  • module (String): The name of the Dust module to use. Defaults to dustjs-linkedin but can also be dust for plain ol' dust, or dustjs-helpers for the LinkedIn Dust build with helpers. If this option is anything other than the default, make sure you have installed the module via npm install.
  • context (Object|String): A JavaScript object to render the template against. This option supports two different types:

String: the location to a file containing valid JSON:

context: "path/to/file.json"

Object: a regular ol' JavaScript object:

context: {
  pageTitle: "My Awesome Website"
}

Array: an array of contexts, either string (files to parse) or JavaScript objects, or both. Each item in the array will be merged into a single context and rendered against the template:

context: [
  "path/to/context.json",
  "path/to/another/context.json",
  { more: "data" }
]

FAQ

  1. Why does the output say undefined?
    Most likely dust is trying to include a file but it can't resove the path properly. Make sure you're setting a basePath option.

Tests

Run npm test.