Webpack(er): Analyze the size of your JavaScript components
We're always striving towards keeping our website's JavaScript as small as possible.
If you're using webpack(er), you can use the webpack-bundle-analyzer plugin to get a good overview, which of your JavaScript modules take up how much space, and where you can optimize.
To use it, add it via npm or yarn
Copyyarn add webpack-bundle-analyzer
Then add this to your environment.js:
Copy// Uncomment this code to show statistics of bundle sizes. Generated file will automatically open in your browser. // Compile with NODE_ENV=production bin/rake assets:precompile const BundleAnalyzerPlugin = require('webpack-bundle-analyzer').BundleAnalyzerPlugin; environment.plugins.append( 'BundleAnalyzer', new BundleAnalyzerPlugin({ analyzerMode: 'static' }) )
Then compile using the production environment. In a Webpacker project, this can be done with
CopyNODE_ENV=production bin/webpack
An interactive graph like this will open in your browser:
The large chunks are the separate bundles (this application uses more than one). Important metrics are "Parsed size" (the amount of JavaScript the browser has to parse) and "Gzipped size" (the amount of data going over the wire).
When done, comment out the code in your environment.js.
You should do check your bundle size at least once before bringing an application into production.
By refactoring problematic code and creating automated tests, makandra can vastly improve the maintainability of your Rails application.
