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

index-hashify

v0.2.0

Published

use sha1 index to browserify row rather than integer

Downloads

3

Readme

index-hashify

version status dependencies devDependencies

A browserify plugin to replace numeric indexes with hashes.

The problem with numeric hashes

browserify uses numbers to identify module functions in the final bundle by default. Since modules are sorted according to their file paths, and those identification numbers are just their corresponding indexes in the sorted array (in most cases), they are prone to changing when dependencies inserted and deleted.

Suppose there are two modules '/a.js' and '/c.js', which will get 1 and 2 as their identification number in the final bundle, respectively. Now if we add require('/b.js') in 'a.js', '/c.js' will get 3 as its identification number even if nothing happens to the original module.

That may cause problems in some cases:

  • common shared bundles. When using factor-bundle, the contents of the common bundle may change due to just the change of identification numbers, invalidating the application cache for it.
  • hot module replacement. Tools like browserify-hmr replace changed modules, but not those who just suffer a identification number change, thus breaking the dependency chain. (See browserify-hmr#28)

This plugin will take the sha1 of the result of concating the file path (relative to basedir) with the contents of the module as the identification number instead, which will not change as long as the module keeps, thus fixing the above problems.

Usage

var b = browserify(opts)
var hashify = require('index-hashify')
b.plugin(hashify)
b.bundle().pipe(process.stdout)