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

jsdoc-plugin-strip-outer-iife

v0.0.2

Published

JSDoc plugin to filter out root-level IIFE before processing

Readme

NAME

jsdoc-plugin-strip-outer-iife - JSDoc plugin to filter out root-level IIFE before processing

INSTALL

mkdir node_modules
npm install jsdoc-plugin-strip-outer-iife
cp node_modules/jsdoc-plugin-strip-outer-iife/strip-outer-iife.js node_modules/jsdoc/plugins/
# create jsdoc.conf.json mentioning this plugin, see below

JSDoc configuration

Sample JSDoc configuration file, e.g. jsdoc.conf.json

{ "plugins": [ "plugins/strip-outer-iife.js" ] }

RUN

jsdoc --configure jsdoc.conf.json inputfile.js

DESCRIPTION

This is a plugin for jsdoc using the jsdoc-plugins system to filter source code before it's seen by the main JSDoc parser to remove the common root-level IIFE's. The intent of this plugin is to:

  • Be harmless in case it doesn't understand your content.
  • Allow comments and whitespace before your root-level IIFE.
  • Ignore any and all IIFE's in the body.
  • Allow anything after the close of the root-level IIFE.
  • Only consider IIFE's that start at the beginning of a line, without whitespace.
  • Only consider IIFE's that end at the beginning of a line, without whitespace.

EXAMPLES

All of these should get removed:

Basic inner

(function(){
    // Whatever is in here gets saved.
}());

Basic outer

(function(){
    // Whatever is in here gets saved.
})();

Browser window

(function(){
    // Whatever is in here gets saved.
})(window);

CoffeeScript

(function(){
    // Whatever is in here gets saved.
}).call(this);

Common inner

/**
 * It's okay to have comments here, these get preserved
 */
// So do single line comments like this
(function(){
    // Whatever is in here gets saved.
}());
// It's also okay to have comments here -- also preserved

LICENSE

This module is licensed under CC0, a kind of internationally-aware "public domain" license, or more properly said: a declaration of my affirmative intent to waive the rights normally reserved under copyright law. You're free to copy, modify, sell for profit, etc, without any need to contact me, give me attribution, reproduce the license text, etc. See LICENSE for the full license text.

TODO

Why not use this module

  • Not using a real JavaScript parser to modify the input stream, only regular expressions.
  • Doesn't use the JSDoc plugin style (yet).
  • Not the right way to fix the problem, see jsdoc-issue-456