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

normalize-js-code

v1.0.2

Published

Normalize javascript code to remove randomness introduced by bundling

Readme

normalize-js-code

normalize-js-code takes javascript code and attempts to normalize it as much as possible by changing variable names in a predictable way. This is useful for comparing minified code, which has short, meaningless variable names that can change unpredictably between builds.

For example, take this code below:

setTimeout(() => console.log(someVariable), 5);

if (true) {
    var someVar = 100;
    let someVariable = 5;
    console.log(someVariable);
}

let someVariable = 'apple';
console.log(someVar);

After normalization, this becomes:

setTimeout(() => console.log(_b), 5);
if (true) {
    var a = 100;
    let b = 5;
    console.log(b);
}
let _b = 'apple';
console.log(a);

The code outputted will be the same regardless of the names of the variables that are inputted, or how it is formatted. If you want around to play with this normalization check out the demo.

Usage

import { normalizeJs } from "normalize-js-code";

const code = `let test = 'hello';`

console.log(normalizeJs(code)); // let a = 'hello';

There is also a normalizeAst function exported if you already have the ast to be normalized.