Analyze webpack stats JSON to identify heaviest assets and duplicate packages, then suggest code-splitting and CDN externalization.
MIT
649,985 tools. Updated 2026-10-10 19:04
"Webpack" matching MCP tools:
- Enumerate Webpack module tables in a selected Chrome tab by injecting a runtime probe and collecting up to a bounded number of modules.MIT
- Generates a Webpack configuration with loaders and plugins from your project directory, eliminating manual setup.MIT
- Analyze Webpack bundles to uncover performance bottlenecks and receive targeted optimization suggestions for reducing bundle size.MIT
- Add optimization settings to Webpack config in a project directory to improve build performance and reduce bundle size.MIT
- Generate a Content Security Policy for an Electron app, accounting for bundler, framework, and dev-mode. Provides meta-tag and session.webRequest variants.MIT
Matching MCP Servers
- FlicenseAqualityBmaintenanceEnables automated migration of JavaScript/TypeScript packages from legacy test runners like Karma, Webpack, and Mocha to Vitest, including AST codemods, multi-project test scaffolding, and self-learning diagnostics for resolving runtime errors.7-
- AlicenseNot gradedqualityDmaintenanceCreates and manages an MCP server integrated with build tools (Rollup, Vite, Webpack, etc.) to enable AI assistants to analyze, inspect, and control the build process.2,813 npm31MIT
- Deploy a folder of web assets (HTML, CSS, JS, or full-stack NextJS) to EdgeOne Pages and receive a public URL.MIT
- Analyze JavaScript source code to detect obfuscation patterns like webpack, JSFuck, or eval-based loaders, and output unpack hints with deobfuscation strategy.MIT
- Learn how to generate the webpack stats file (.next/stats.json) required for bundle attribution. Choose a manual recipe or an automatic action plan for Copilot to execute.MIT
- Compare technologies like frameworks, libraries, databases, or programming languages side-by-side. Automatically gather structured information to support informed decision-making.MIT
- Pinpoint npm packages and app code dominating shared chunks, with unminified sizes and byte shares, to reveal what bloats common bundles.MIT
- Analyze Next.js build evidence to return severity-ranked, concrete bundle optimizations with byte-size impact and actionable changes.MIT
- Trace import chains from entry points to identify why a module is bundled, showing dependency paths and unminified webpack module size. Requires webpack stats loaded first.MIT
- Parses the webpack module stats file (.next/stats.json) and links it to a loaded build, enabling tools to detect duplicates, explain shared chunks, trace imports, and suggest optimizations.MIT
- Retrieve page metadata—title, URL, visibility, doctype, charset, meta tags, scripts, styles, links, forms—to inspect rendering state and dev-server overlays.MIT
- Map a generated code location (line and column) back to the original source using source maps, enabling debugging of bundled or transpiled code like TypeScript, Babel, webpack, or esbuild.Apache 2.0
- Resolve dynamic bundle references (webpack://, ng://, Vite /@fs/) to raw file paths for accurate stack trace decoding.MIT
- Configure build system settings for DHIS2 applications, including entry points, PWA features, proxy setup, and custom authorities.MIT
- Generate and fix proxy configurations for local development to connect with DHIS2 instances, supporting webpack, React, Vite, and custom setups.MIT
- Map any error message or symptom description to a verified fix. Input a concrete error stack or free-text query to receive exact-match solutions or search results with confidence scores and source URLs.-
- Query the local manifest registry to discover package exports, symbol kinds, and side effects for npm dependencies.-