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

webpack-fingerprint

v0.2.0

Published

Generate list of all libraries imported in bundling process and their versions.

Downloads

4

Readme

Webpack Fingerprint Plugin

This plugin will generate list of node modules (along with their version and licence) which were imported into the bundle and place it in an JSON file

The most common usage will be for tracking what versions are deployed with current version of your application and tracking their licenses for legal requirements.

Installation

The plugin is available via npm:

$ npm install --save webpack-fingerprint

Examples

Basic

var WebpackFingerprint = require("webpack-fingerprint");

module.exports = {
  plugins: [    
    new WebpackFingerprint({
      filename: "fingerprint.json" // Default
    })
  ]
}

Will produce a file called fingerprint.json with following info:

{
  "date": "2017-09-17T15:56:50.468Z",
  "version": "1.0.0",
  "packages": {
    "babel-loader": {
      "version": "7.1.2",
      "license": "MIT"
    }
    "react": {
      "version": "15.6.1",
      "license": "BSD-3-Clause"
    }
    "react-dom": {
      "version": "15.6.1",
      "license": "BSD-3-Clause"
    }
  }
}

Custom information

You can provide additional information to also be stored in the resulting file. To do so, pass a additional field on the configuration object.

var WebpackFingerprint = require("webpack-fingerprint");

module.exports = {
  plugins: [    
    new WebpackFingerprint({
      additional: {
        build_number: process.env.CI_BUILD_NUMBER
      }
    })
  ]
}

Custom package details

You can also provide a transformer that will allow you to change the default information stored for each package. To do so, provide a transformer function, which will be called with each module package.json file and its return value will be used. If null is returned by all transformers, the package field will be omitted.

var WebpackFingerprint = require("webpack-fingerprint");

module.exports = {
  plugins: [    
    new WebpackFingerprint({
      transformer: (package) => ({
        version: package.version,
        author: package.author
      })
    })
  ]
}