You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 38fbae3
Browse filesBrowse the repository at this point in the historyBrowse files
|`module-graph`| The Vite dev server's module graph: the entries, the lazy boundaries (`import()`) with the modules and size each pulls in, and the biggest modules. With `search`, matching modules with their importers, imports and `import()` calls. |`search`, `limit`|
1061
-
|`chunk-sizes`| The chunks of the last production build: initial or lazy, size, gzip size, and with `stats.json` the entry point. |`limit`|
|`module-graph`| The Vite dev server's module graph: the entries, the lazy boundaries (`import()`) with the modules and size each pulls in, the biggest modules, and the slowest modules with the wall-clock time Vite spent resolving, loading and transforming each. With `search`, matching modules with their size, time, importers, imports and `import()` calls. |`search`, `limit`|
1061
+
|`chunk-sizes`| The chunks of the last production build: initial or lazy, size, gzip size, and with `stats.json` the entry point. |`limit`|
1062
1062
1063
1063
`module-graph` needs the Vite plugin, in the dev server's process; it reads nothing on the stdio MCP server. Sizes are transformed, unminified code, for modules the browser requested. `chunk-sizes` reads the build output on disk, so it works anywhere the project is, and says how to build when there is none. `limit` defaults to 20 for `module-graph` (at most 200) and 30 for `chunk-sizes` (at most 500).
0 commit comments