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-embersmith

v0.0.1

Published

A grunt task and helpers for invoking the embersmith static site generator

Downloads

3

Readme

grunt-wintersmith

A grunt task for working with the Embersmith static site generator.

Getting Started

This plugin requires Grunt ~0.4.0

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

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

grunt.loadNpmTasks('grunt-embersmith');
  • This plugin was designed to work with Grunt 0.4.x. If you're still using grunt v0.3.x it's strongly recommended that you upgrade.

Embersmith task

Run this task with the grunt embersmith command.

Each task may include options for setting both the action and the configuration file to be used.

Options

action

Type: String Default: 'build'

This value currently supports 'build' or 'preview'. If you use 'build' it will build the site with Embersmith using either the default or the user defined config file. If you use 'preview', it will run the Embersmith preview server for either the default or the user defined config file. Any other value will result in an error.

It is important to note that 'preview' is an asychronous task which will run until you end it. If you want to utilize this alongside a similar task (like grunt-contrib-watch), you will either need to use another command line window or utilize a grunt plugin which allows for concurrent tasks (like grunt-concurrent).

config

Type: String Default: './config.json'

The configuration file to use for the specified task. By default it utilizes './config.json', but if you need another value, you may specify it here.

Sample Grunt Files

If you are utilizing the standard value for config, (which is ./config.json), then you can simply define your tasks as follows:

module.exports = function(grunt) {
  
  grunt.initConfig({
    
    embersmith: {
      build: {},
      preview: {
        options: {
          action: "preview"
        }
      }
    }
    
  });

  // Load NPM Task
  grunt.loadNpmTasks('grunt-embersmith');

};

In situations where you want to define separate environments which have separate configurations, or if you need to utilize another configuration file, you can include the config option within the options object:

module.exports = function(grunt) {
  
  grunt.initConfig({
    
    embersmith: {
      staging: {
        options: {
          config: './config-staging.json'
        }
      },
      production: {
        options: {
          config: './config-production.json'
        }
      },
      preview: {
        options: {
          action: "preview",
          config: './config-preview.json'
        }
      }
    } 
  });

  // Load NPM Task
  grunt.loadNpmTasks('grunt-embersmith');

};

Credit

This code is based on grunt-wintersmith by David Tucker and adam j. sontag.