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

unparam

v0.1.0

Published

Node module used to explicitly silence jslint's unparam warnings

Downloads

26

Readme

unparam Build Status Coverage Status

NPM

Easily ignore (or track) unused parameters, variables, functions, etc. Just call unparam with them!

Usage

var unused = require('unparam');

function(arg1,arg2){
    unused(arg1);
    do_something(arg2);
}

It's that easy!

Advanced usage

If you want to track all of your unused parameters, set the UNPARAM_TRACE environment variable. This will turn on tracking of each call, and will generate a report with line numbers, filenames, columns, (optionally source lines) and a total count of unused parameters. If you want the actual call to unparam to show up in the report, set the UNPARAM_READ_FILE environment variable. If you don't want the report to write to stdout, set the UNPARAM_WRITE_FILE environment variable.

$ UNPARAM_TRACE=true UNPARAM_READ_FILE=true node app.js
{ '/path/to/file.js': 
   [ { column: 5,
       lineNumber: 6,
       filename: '/path/to/file.js' } ] }
$
$ UNPARAM_TRACE=true UNPARAM_READ_FILE=true UNPARAM_WRITE_FILE=report.json node app.js
$ cat report.json
]
   {"column":5,"lineNumber":6,"filename":"/Users/gcochard/unparam/test/function.js"}
]
$

Super ultra advanced usage

If you want to have multiple reports or different types of behavior based on the file/module/etc, don't bother with environment variables. The function that unparam exports is also a constructor! Call it with new and pass in your options like so:

var path = require('path')
var Unparam = require('unparam');
var unused1 = new Unparam({trace:true,readFile:true,writeFile:path.join(__dirname,'report1.json')});
var unused2 = new Unparam({trace:true,readFile:false,writeFile:path.join(__dirname,'report2.json')});

function(arg1,arg2,arg3){
    unused1(arg1);
    unused2(arg2);
    do_something(arg3);
}