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

stats-reporter-webpack-plugin

v1.1.3

Published

Stats reporting for webpack

Downloads

56

Readme

Stats reporting plugin for webpack

Build Status Coverage Status dependencies Status devDependencies Status peerDependencies Status semantic-release Greenkeeper badge

Send the stats of a build to a reporting service. Currently DataDog is the only reporter implemented.

Installation

npm install --save-dev stats-reporter-webpack-plugin

Usage

const { StatsPlugin, DataDogStatsReporter } = require('stats-reporter-webpack-plugin');

module.exports = {
  plugins: [
    new StatsReporterPlugin({
      test:
      reporter: new DataDogStatsReporter({
        apiKey: process.env.DD_API_KEY,
        metricName: 'my-app.assets',
        tags: ['app:my-app', 'env:production'],
        test: /(js|css)$/
      })
    })
  ]
};

API

StatsReporterPlugin

new StatsReporterPlugin(options: StatsReporterPluginOptions);

StatsReporterPluginOptions fields

  • reporter: StatsReporter: The reporter to use for sending stats.

Stats Reporters

DataDogStatsReporter

new DataDogStatsReporter(options: DataDogStatsReporterOptions);
DataDogStatsReporterOptions fields
  • apiKey: string: Your DataDog API key
  • gzipSize?: boolean = true: Report gzipped size if true, uncompressed size if false
  • metricName: string: The base name for the metric
  • tags?: string[]: Custom tags for the metric. The following tags are always added:
    • chunk: the chunk name
    • type: the type of asset (js, css, etc)
  • test?: RegExp: Test to match files against. If not set, stats for all emitted assets will be sent.