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 🙏

© 2026 – Pkg Stats / Ryan Hefner

grunt-sitemap

v2.0.1

Published

Grunt sitemap generator plugin

Readme

grunt-sitemap

A Grunt plugin for generating sitemaps

NPM version Build Status Dependency Status devDependencies Status

Installation

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

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

grunt.loadNpmTasks('grunt-sitemap');

Configuration

sitemap is a multitask, so you can use it similarly to lint, watch etc...

grunt.initConfig({
  sitemap: {
    dist: {
      pattern: ['**/*.html', '!**/google*.html'], // this will exclude 'google*.html'
      siteRoot: 'public/'
    }
  }
});

Options

siteRoot

  • Type: string
  • Default: ./

Site (public root) directory relative to your Gruntfile.js file. This is where indexing will begin and your sitemap be saved to.

pattern

  • Type: string
  • Default: /**/*.html

Pattern to match website files. Excludes 404.html by default and converts index.html to directory path /. See minimatch for more on pattern matching.

homepage

  • Type: string
  • Default: read from package.json

Site URL including protocol: e.g. http://www.example.com If the homepage field is specified in your package.json, it will be used from there.

changefreq

  • Type: string
  • Default: daily

Set this to override <changefreq> in sitemap.

priority

  • Type: string
  • Default: 0.5

Set this to override <priority> in sitemap.

extension

  • Type: object
  • Default: { required: true }

E.g.

extension: {
  required: false
}

If you need a trailing slash just set the attribute trailingSlash: true. E.g.

extension: {
  required: false,
  trailingSlash: true
}

By default the <loc> tag is generated for paths that contain file extensions. E.g.: .html or .htm. If you don't want URLs with file extensions to be included in your sitemap, just add the attribute extension: { required: false }. This will output URLs without file extensions.

Contributing

We accept pull requests! A special thanks to XhmikosR for keeping things rolling.