webpack-stats-diff-plugin - npm Package Compare versions

Comparing version 0.1.0 to 0.2.0

package.json

 {
   "name": "webpack-stats-diff-plugin",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Webpack plugin to report changes in bundle sizes across builds",
@@ -9,3 +9,4 @@ "main": "src/index.js",
     "lint": "eslint 'src/**'",
-    "test": "jest --passWithNoTests"
+    "test": "jest --passWithNoTests",
+    "semantic-release": "semantic-release"
   },
@@ -49,4 +50,4 @@ "repository": {
   "dependencies": {
-    "webpack-stats-diff": "1.0.2"
+    "webpack-stats-diff": "1.2.0"
   }
 }

README.md

 # webpack-stats-diff-plugin
 
-Webpack plugin for reporting changes in bundle sizes across builds
+Clear reporting of bundle sizes relative to a prior build. This is particularly useful for understanding the outcome of webpack configuration changes.
+
+## Why is this useful?
+
+Webpack logs the absolute sizes of bundles, but it's hard to see the overall impact of a code or configuration change. For projects with more than a few assets, it's nearly impossible. For example, if you wanted to see the effect of changing webpack's `optimization.splitChunks.chunks` from its default `"async"` value to the recommended `"all"`, instead of trying to compare the standard webpack outputs
+
+![standard webpack report with chunks: async](readme-assets/standard-report-all.png)
+
+![standard webpack report with chunks: all](readme-assets/standard-report-all.png)
+
+Adding this webplack plugin will highlight only the key changes:
+
+![webpack-stats-diff-plugin comparison output](readme-assets/plugin-output.png)
+
+## Installation & Usage
+
+```
+npm install webpack-stats-diff-plugin --save-dev
+```
+
+To establish a baseline to compare to, you'll need the build to output a json stats file. This can be done by adding an npm script like `"build_stats": "webpack --profile --json > stats/master.json"` or using [webpack-stats-plugin](https://github.com/FormidableLabs/webpack-stats-plugin) with `opts.fields` containing `"assets"`.
+
+Add the following to your webpack config to conditionally use the plugin when passed a CLI flag:
+
+<!-- prettier-ignore -->
+```javascript
+const WebpackStatsDiffPlugin = require('webpack-stats-diff-plugin');
+
+module.exports = (env = {}) => {
+  // ... other webpack config
+  plugins: [
+    // ... other plugins
+    env.oldStatsFile && new WebpackStatsDiffPlugin({
+      oldStatsFile: env.oldStatsFile
+    })
+  ].filter(Boolean)
+};
+```
+
+To see your changes since that prior build, add on the flag to your existing webpack build command. For example,
+
+```
+npm run build -- --env.oldStatsFile=stats/master.json
+```
+
+### Additional configuration
+
+The WebpackStatsDiffPlugin constructor can also take in the following fields:
+
+- `extensions`: An array of strings, optionally with a leading period. If provided, only asset files matching a given extension will be displayed and used for calculating totals. For example, `extensions: ['.js']` will only show size changes for built javascript files.
+
+- `threshold`: Minimum difference percentage to qualify as a significant change. This prevents flooding the output with files that have only trivially changed their compiled output. Defaults to `5`. Can set to 0 to see all changes.

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

1093951

increased by691.59%

Number of package files

12

increased by50%

Number of lines in readme file

55

increased by1275%

Dependency changes

• + Addedwebpack-stats-diff@1.2.0(transitive)

• - Removedwebpack-stats-diff@1.0.2(transitive)

• Updatedwebpack-stats-diff@1.2.0