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

cleanjs

v1.0.1

Published

Replaces all the require(file.js) and export statements in file with the actual file cotent, and compiles them into one single perfect JavaScript file for the whole project.

Readme

Clean JS

Replaces all the require and export statements in file with the actual js file content, and compiles them into one single perfect JavaScript file for the whole project.

Get Started

This guide will help you get started with cleanJS in no time. Using Clean JS is as eas an installing it, requiring and running it.

You can , also clean source-maps statements from a file for a clean flat file with no extra code for external dependence tree modulation.

Prerequisites

To use this module you will need NodeJs and npm installed on your system

Give examples

Installing

  1. Get this clean.js into project root directory.

  2. Require clean.js file into your gulp or grunt

let Clean = require("perfect.js").Clean;

new Clean("from/raw/files.js","to/clean/single.js")
  1. If you want to watch the files for changes go ahead
new Perfect("from/raw/files.js","to/clean/single.js").watch()

As of now this supports cleaning of js files directly so long there is require(files) to be converted to a single file js.

When using TypeScript give the link to your compiled entry.js file as the first argument to Perfect.

Results and benefits

A successful Clean JS run gives you :-

  1. A clean single JavaScript file
  2. Less code unlike what you get when using build sytem/browserify
  3. Its straight forward and browser compatible js
  4. Improved code readability
  5. A simple new file while leaving your project intact
  6. Live Updates as project file/s change
  7. Satisfaction fro getting rid of unnecessary require overhead from project.