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 🙏

© 2025 – Pkg Stats / Ryan Hefner

grunt-comment-toggler

v0.2.2

Published

Toggle comments inside build blocks.

Readme

grunt-comment-toggler

Toggle comments inside build blocks.

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-comment-toggler --save-dev

The "toggleComments" task

toggleComments searches files for build blocks and comments or uncomments individual lines or a whole block depending on the command and delimiter specified in the build block.

Build blocks

Build blocks are defined using the following syntax:

<!-- comments:(command) (comment delimiter) -->
Your code goes here
<!-- endcomments -->
  • command is the type of processing done for each line. Following commands are supported:

    • comment, uncomment and toggle for using line comments.
    • comment-block, uncomment-block and toggle-block for block comments. Block commenting only supports special delimiters.
  • comment delimiter is the delimiter used for comments. Any sequence of non-whitespace characters is valid. There are two special delimiters that can be used.

Special delimiters

For HTML and CSS specifying a single delimiter for comments isn't enough. For this purpose there are two special delimiters html and css that use appropriate block comments to process each line or the whole block. See examples on how to use them.

Options

padding

Type: Number
Default: 1

Amount of whitespace between the comment delimiters and the line content.

removeCommands

Type: Boolean
Default: false

When true, removes the <!-- comments:... --> and <!-- endcomments --> definitions from the file during processing. Can be used to prevent conflicts with other Grunt plugins that use similar build block syntax.

Examples

Basic uncommenting example

Example using a single character to uncomment line

# <!-- comments:uncomment # -->
# AddHandler application/x-httpd-php54 .php
# <!-- endcomments -->

HTML & CSS line and block examples

How to process HTML and CSS block comments using special delimiters

<style>
    /* <!-- comments:toggle css --> */
    p {color: red}
    /* p {color: blue} */
    /* <!-- endcomments --> */
    
    /* The code above will swap the color from red to blue */
</style>

<!-- comments:comment html -->
<p>This line will be commented</p>
<!-- endcomments -->

<!-- comments:uncomment-block html -->
<!--
<p>
  This whole block will be uncommented.
  Useful for production only JavaScript
  and CSS, where commenting each line
  individually would be inconvenient.
</p>
-->
<!-- endcomments -->

Custom options example

This example shows the usage of custom options as well as a sample output.

Gruntfile.js

toggleComments: {
    customOptions: {
        options: {
            padding: 4,
            removeCommands: true
        },
        files: {"targetfile.js": "testfile.js"}
    }
}

testfile.js

// <!-- comments:comment // -->
var txt = "This will be commented with the padding";
// var txt2 = "This line will not have padding, since it's already commented";
// <!-- endcomments -->
var txt3 = "This is not affected";

Outputs the following in targetfile.js


//    var txt = "This will be commented with the padding";
// var txt2 = "This line will not have padding, since it's already commented";

var txt3 = "This is not affected";

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.

Changelog

0.2.0 - 2014-07-17

  • Added support for block comments

0.1.0 - 2014-06-06

  • Initial release