Warning
Vite's enable minify by default.There for you will see that the parsed size is larger than actual size.This is because the bundle info provide by rollup isn't compressed.(If you care about this problem you can choose anothr plugins.)
$ yarn add vite-bundle-analyzer -D
# or
$ npm install vite-bundle-analyzer -Dimport { defineConfig } from 'vite'
import { analyzer } from 'vite-bundle-analyzer'
export default defineConfig({
plugins: [
// ...your plugin
analyzer()
]
})
// If you are using it in rollup you can import 'adapter' from package.
// Then use it with adapter(analyzer())| params | type | default | description |
|---|---|---|---|
analyzerMode |
server|static|json |
server |
In server will create a static server to preview. |
fileName |
string |
stats |
The name of the static product.（No need to include .ext name） |
reportTitle |
string |
plugin name |
Report website title. |
gzipOptions |
Record<string,any> |
{} |
Compression options. (details see zlib module) |
analyzerPort |
number|'auto' |
8888 |
static server port. |
openAnalyzer |
boolean |
true |
Open the static website. (Only works on analyzerMode is server ) |
summary |
boolean |
true |
Show full chunk info to stdout. |
Contributions are welcome! If you find a bug or want to add a new feature, please open an issue or submit a pull request.
If you're using vite you can get the logs with vite build --debug and then extreact the part relevant to analyze plugin. Or using cross-env to setup ANALYZE_DEBUG=true in your local.
env.
If you're use a plugin that break the sourcemap it will affect the analyze plugin. I know it's stupid, But is the way to get the size close to the actual size. Like @vitejs/plugin-legacy don't prvide
the correctly sourcemap for legacy chunk. For some reason, no analysis will be provided for those module.