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

npm-prestige

v1.1.1

Published

Finds and summarizes duplicate npm dependencies

Downloads

4

Readme

npm-prestige

Check and report duplicate -> [email protected] dependencies -> [email protected] inside your installed npm modules

Usage

npm -g i npm-prestige or yarn global add npm-prestige

npm-prestige

Summary

When building large js applications, you sometimes end up with large trees of dependencies. When different dependencies depend on different versions of the same package your final program/bundle will end up with both versions inside. Depending on your application, these extra packages may have negative performance implications (for example if you're developing js for a web application, it will increase the final bundle size the user needs to download over the wire).

Sometimes it gets worse, as npm and yarn won't always dedupe all versions of a package with the same version (if there's another version of the package already installed higher up in the dependency tree) This can lead to the exact same version of a package installed many many times. Note that browserify and some other tools match and dedupe based on the code signature for different dependencies and don't have this problem

Updating your dependencies to all use the same semver range of packages can reduce the final bundle size of your packages.

npm-prestige reports all duplicate dependencies that it finds installed. It uses npm ls under the hood, and only reports un-deduped packages.

NPM version

Since npm-prestige uses npm under the hood, it has a hidden dependency on the version of npm you've globally installed. It works fine with all versions of npm that I've tested (4.1.0 and up), but prints nicer output with >4.6.0. Please submit an issue if it doesn't work with a specific version of npm