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-jinja-new-grunt

v0.5.0

Published

A grunt plugin for compiling Jinja2 templates with nunjucks.

Downloads

38

Readme

grunt-jinja

A grunt plugin for compiling Jinja2 templates with James Long's awesome nunjucks templating system.

Getting Started

This plugin requires Grunt ~0.4.1

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-jinja --save-dev

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

grunt.loadNpmTasks('grunt-jinja');

The "jinja" task

Overview

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

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

Options

options.templateDirs

Type: Array Default value: [path.join(process.cwd(), 'templates')]

A an array of paths in which your templates can be found. If not provided, this will default to the "templates" directory at the same level as your Gruntfile.

options.contextRoot

Type: String Default value: path.join(process.cwd(), 'template-context')

The directory in which your template context files can be found. grunt-jinja will look in this directory to find JSON documents or node modules that correspond to your template names and use them for that template. For example, if you use a template "products/phones.html", you can create a "products/phones.json" or "products/phones.js" file in the context root and it will be used as context when rendering the template. To add context to all of your templates, create an "_all.json" or "_all.js" file in the context root.

options.filters

Type: Object Default value: {}

An object whose keys are filter names and values are functions. Each pair will be registered with the template environment using the addFilter method.

Other options

Other options are passed directly to the nunjucks environment object. Currently, valid options are as follows:

options.dev

Type: Boolean Default value: false

A boolean which, if true, puts nunjucks into development mode which means that error stack traces will not be cleaned up.

options.autoescape

Type: Boolean Default value: true

A boolean which, if true, will escape all output by default See Autoescaping.

options.tags

Type: Object Default value: {}

An object specifying custom block start and end tags. See Customizing Variable and Block Tags.

Usage Examples

Default Options

In this example, the default options are used to compile a templates in the "templates/" directory to the "built" directory:

grunt.initConfig({
  jinja: {
    files: {
      'built/index.html': 'templates/index.html'
    },
  },
})

This example compiles all templates that don't begin with an underscore:

grunt.initConfig({
  jinja: {
    dist: {
      files: [{
        expand: true,
        dest: 'built/',
        cwd: 'templates/',
        src: ['**/!(_)*.html']
      }]
    }
  }
})

Custom Options

In this example, custom options are used to load the templates from directories other than "templates":

grunt.initConfig({
  jinja: {
    dist: {
      options: {
        templateDirs: ['src/templates']
      },
      files: {
        'built/index.html': 'src/templates/index.html'
      }
    }
  }
})