42cff0a09c
* Move next-bundle-analyzer to Next.js repo * Remove options from bundle-analyzer
33 lines
762 B
Markdown
33 lines
762 B
Markdown
# Next.js + Webpack Bundle Analyzer
|
|
|
|
Use `webpack-bundle-analyzer` in your Next.js project
|
|
|
|
## Installation
|
|
|
|
```
|
|
npm install --save @next/bundle-analyzer
|
|
```
|
|
|
|
or
|
|
|
|
```
|
|
yarn add @next/bundle-analyzer
|
|
```
|
|
|
|
### Usage with environment variables
|
|
|
|
Create a next.config.js (and make sure you have next-bundle-analyzer set up)
|
|
|
|
```js
|
|
const withBundleAnalyzer = require("@next/bundle-analyzer")({ enabled: process.env.ANALYZE === "true" });
|
|
module.exports = withBundleAnalyzer({});
|
|
```
|
|
|
|
Then you can run the command below:
|
|
|
|
```bash
|
|
# Analyze is done on build when env var is set
|
|
ANALYZE=true yarn build
|
|
```
|
|
|
|
When enabled two HTML files (client.html and server.html) will be outputted to `<distDir>/analyze/`. One will be for the server bundle, one for the browser bundle.
|