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-handlebars-layout

v0.0.2

Published

Parse HTML files as Handlebars templates using Handlebars layout.

Downloads

32

Readme

grunt-handlebars-layout

Parse HTML files as Handlebars templates using Handlebars layout.

Getting Started

This plugin requires Grunt ~0.4.5

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-handlebars-layout --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-handlebars-layout');

The "handlebars_layout" task

Overview

In your project's Gruntfile, add a section named handlebars_layout to the data object passed into grunt.initConfig().

grunt.initConfig({
  handlebars_layout: {
    options: {
      // Task-specific options go here.
    },
    your_target: {
      // Target-specific file lists and/or options go here.
    },
  },
})

Options

options.basePath

Type: String Default value: process.cwd()

Establish the base line for partials. For example, given this structure:

├── myproject
│   ├── partials
        └── layout.html

If your Gruntfile is along with myproject then a Partial will be registered with the following name: myproject\partials\layout.

But if you want your partials to start from partials just provide a basePath of myproject/partials and a partial with just layout will be registered.

options.partials

Type: String or Array Default value: []

A string or an array of files (or globs) from which load partials

options.helpers

Type: String or Array Default value: []

A string or an array of files (or globs) from which load helpers

options.data

Type: String, Object or Array Default value: {}

If you provide a String, it must be a path to a JSON or YAML file, from which load data to pass to Handlebars.

You can also pass a plain Object which will be used instead.

Finally, you can also pass an Array of paths which can include globs as well. Note that, in the event of loading more than one data file, the data will be namespaced with the name of the file. For example. Given this two files being loaded, with the same data:

data/global.json data/mymodule.json

{ 'name' : 'My name' }

The data from global would be in {{ global.name }}

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Release History

(Nothing yet)