nonzzz / vite-bundle-analyzer

bundle analyzer for vite

Hi there 👋

• You can call me Kanno
• I've been busy recently
• Learning zig

vite-bundle-analyzer's Issues

Module sizes

Currently all npm packages have same size in UI, while some may be 10kb and others 1mb. Can you please make modules size based on their size in bundle? It works like that in webpack-bundle-analyzer

Output file is empty (with solution)

On my M1 macbook pro the output file is completely empty, 0 bytes

My setup/project:

• M1 macbook pro (32gb ram)
• Nx repo
• Vite
• Analyser running in 'static' mode

I found the problem was not awaiting the write of the output file and have included a fix here: #21

Request to add a configuration item. The default value for Treemap Sizes is Parsed

Invalidate Option `analyzerMode` 打包报错

最新版
analyzer({
openAnalyzer: false, // 是否打开静态网站
}),
只配置了一个参数
"devDependencies": {
"@vitejs/plugin-legacy": "^5.3.2",
"@vitejs/plugin-vue": "^5.0.4",
"rollup-plugin-visualizer": "^5.12.0",
"unplugin-auto-import": "^0.17.5",
"unplugin-vue-components": "^0.26.0",
"vite": "^5.2.9",
"vite-bundle-analyzer": "^0.9.4",
"vite-plugin-compression2": "^1.1.0"
}

analyzerPort is 'atuo' instead of 'auto'

https://github.com/search?q=repo:nonzzz/vite-bundle-analyzer%20atuo&type=code

Crash on build

I can't get it to work on a freshly created SvelteKit project.
Excuse me if it's just a knowledge gap and I am missing what this project is actually for.

Steps to reproduce:

1. npm create svelte@latest my-app
2. add vite-bundle-analyzer to vite.config.ts
3. npm run build

error during build:
TypeError: Cannot read properties of null (reading 'port')
    at get port [as port] (file:///Users/peter/code/local-first/vite-bundle-test/node_modules/.pnpm/[email protected]/node_modules/vite-bundle-analyzer/dist/index.mjs:2:7940)
    at Object.closeBundle (file:///Users/peter/code/local-first/vite-bundle-test/node_modules/.pnpm/[email protected]/node_modules/vite-bundle-analyzer/dist/index.mjs:2:10477)
    at file:///Users/peter/code/local-first/vite-bundle-test/node_modules/.pnpm/[email protected]/node_modules/rollup/dist/es/shared/node-entry.js:19778:40
    at async Promise.all (index 0)
    at async PluginDriver.hookParallel (file:///Users/peter/code/local-first/vite-bundle-test/node_modules/.pnpm/[email protected]/node_modules/rollup/dist/es/shared/node-entry.js:19706:9)
    at async Object.close (file:///Users/peter/code/local-first/vite-bundle-test/node_modules/.pnpm/[email protected]/node_modules/rollup/dist/es/shared/node-entry.js:20635:13)
    at async build (file:///Users/peter/code/local-first/vite-bundle-test/node_modules/.pnpm/[email protected]/node_modules/vite/dist/node/chunks/dep-cNe07EU9.js:67497:13)
    at async CAC.<anonymous> (file:///Users/peter/code/local-first/vite-bundle-test/node_modules/.pnpm/[email protected]/node_modules/vite/dist/node/cli.js:842:9)

You can also check out the codesandbox or the minimal repo showcasing the error.

Feature possiblity: add stdout option to analyzerMode

Not sure if you're open to requests, but I'm mainly looking for a decent summary of the build output in the terminal. This makes most sense on a build server as well because the final build does not need to have a fancy result. Something like the following is more than enough: 16 chunks of 876 kB (parsed: 432 kB | gzipped: 123 kB)