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-remove-calls

v0.0.6

Published

Grunt task to remove method calls statements

Readme

grunt-remove-calls

This Grunt task removes all the method calls statementss from the Javascript files.

It is based on the grunt-remove-logging project using the next license:

/*!
 * Grunt Remove Logging
 * https://github.com/ehynds/grunt-remove-logging
 *
 * Copyright (c) 2013 Eric Hynds
 * Licensed under the MIT license.
 */

In order to satisfy the clauses of the MIT license, this project must use this license too.

Installation

Before to run the task, it is necessary to have installed the Grunt application installing the command line interface: installing the CLI.

Install this plugin adding it to the package.json file or using the next command:

npm install grunt-remove-calls

Documentation

The task must be configured in the project Gruntfile.js file adding the NPM task:

grunt.loadNpmTasks('grunt-remove-calls');

To configure it, there is two parameters:

  • src: source file path, file the statements will be removed.
  • dest: destination file path, this file will be created with the resulting source-code.

However, without specifying the namespaces and methods the task will do nothing.

  • options.namespaces: list of namespaces (default value: []).
  • options.methods: list of methods of the namespaces to remove (default value: []).

Example of Gruntfile.js configuration:

grunt.loadNpmTasks('grunt-remove-logging');

grunt.initConfig({
  removecalls: {
    dist: {
      src: 'app.js',
      dest: 'app-clean.js',
      options: {
        namespaces: [
          'logger'
        ],
        methods: [
          'log',
          'debug'
        ]
      }
    }
  }
});

To run this task against multiple files and automatically overwrite them with the resultant output, just omit the dest option:

grunt.loadNpmTasks('grunt-remove-logging');

grunt.initConfig({
  removecalls: {
    dist: {
      src: 'tmp/**/*.js',
      options: {
        namespaces: [
          'logger'
        ],
        methods: [
          'log',
          'debug'
        ]
      }
    }
  }
});

Optional configuration properties

This plugin can be customized by specifying the following options:

  • replaceWith: value to replace the statements with; the default option is an empty string.
    • Note: for fancy statements like console && console.log('foo'); it is necessary to specify a value like 0; so that the scripts do not completely break.

Skipping Individual Statements

It is possible to keep specific call statements by adding the comment directive /*remove-calls:skip*/ after the statement:

object.method('foo');/*remove-calls:skip*/
object.method('foo')/*remove-calls:skip*/;
console.log('foo') /* remove-calls:skip */;