Analyze Bundle
- 135 installs
- 1.6k repo stars
- Updated July 9, 2026
- vercel-labs/dev3000
dev3000 skill converting Next.js bundle analyzer output to NDJSON for exploration.
About
dev3000 skill for analyzing Next.js bundle size data. Converts bundle analyzer reports to NDJSON format for programmatic exploration and filtering. Enables identifying large modules, duplicate dependencies, and optimization targets in Next.js production builds. Used when investigating client or server bundle bloat after running the Next.js bundle analyzer, feeding structured data into further analysis or reporting workflows within the dev3000 tooling family.
- Converts Next.js bundle analyzer data to NDJSON format
- Enables programmatic exploration of bundle module sizes
- Identifies large dependencies and duplicate packages
- Part of dev3000 performance analysis tooling
- Supports filtering and querying bundle composition data
Analyze Bundle by the numbers
- 135 all-time installs (skills.sh)
- +1 installs in the week ending Jul 27, 2026 (Skillselion tracking)
- Ranked #978 of 2,277 Frontend Development skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
analyze-bundle capabilities & compatibility
- Capabilities
- convert bundle to ndjson · explore bundle modules
- Works with
- vercel
- Use cases
- frontend · testing
What analyze-bundle says it does
Convert Next.js bundle analyzer data to NDJSON and explore it
npx skills add https://github.com/vercel-labs/dev3000 --skill analyze-bundleAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 135 |
|---|---|
| repo stars | ★ 1.6k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 9, 2026 |
| Repository | vercel-labs/dev3000 ↗ |
How do I analyze Next.js bundle composition programmatically?
Convert Next.js bundle analyzer output to NDJSON and explore bundle composition for performance optimization.
Who is it for?
Developers optimizing Next.js bundle size with structured analyzer output.
Skip if: Runtime performance profiling unrelated to bundle analyzer data.
When should I use this skill?
User needs to convert or explore Next.js bundle analyzer data in dev3000 workflow.
What you get
Bundle analyzer data converted to NDJSON ready for exploration and optimization decisions.
Files
analyze-to-ndjson
Converts Next.js bundle analyzer binary .data files into grep/jq-friendly NDJSON.
Analyze artifacts
This workflow pre-generates analyzer artifacts in:
.next/diagnostics/analyze/ndjson/routes.ndjson.next/diagnostics/analyze/ndjson/sources.ndjson.next/diagnostics/analyze/ndjson/output_files.ndjson.next/diagnostics/analyze/ndjson/module_edges.ndjson.next/diagnostics/analyze/ndjson/modules.ndjson
Focus on reading these files and using their evidence to prioritize changes.
Output files
| File | What's in it |
|---|---|
modules.ndjson | Global module registry (id, ident, path) |
module_edges.ndjson | Module dependency graph (from, to, kind: sync/async) |
sources.ndjson | Per-route source tree with sizes and environment flags |
chunk_parts.ndjson | Granular size data: one line per (source, output_file) pair |
output_files.ndjson | Per-route output files with aggregated sizes |
routes.ndjson | Route-level summaries |
Browsing the output
Route overview
jq -s 'sort_by(-.total_compressed_size)' .next/diagnostics/analyze/ndjson/routes.ndjsonFind large sources
jq -s '
group_by(.full_path)
| map(max_by(.compressed_size))
| sort_by(-.compressed_size)
| .[0:10]
| .[] | {full_path, compressed_size, size, route}
' .next/diagnostics/analyze/ndjson/sources.ndjsonClient-side JS
grep '"client":true' .next/diagnostics/analyze/ndjson/sources.ndjson \
| grep '"js":true' \
| jq -s 'sort_by(-.compressed_size) | .[0:10] | .[] | {full_path, compressed_size}'Module dependencies
grep '"from":42,' .next/diagnostics/analyze/ndjson/module_edges.ndjson | jq .to
grep '"to":42,' .next/diagnostics/analyze/ndjson/module_edges.ndjson | jq .from
grep 'react-dom' .next/diagnostics/analyze/ndjson/modules.ndjson | jq '{id, path}'Output files for a route
grep '"route":"/"' .next/diagnostics/analyze/ndjson/output_files.ndjson \
| jq -s 'sort_by(-.total_compressed_size) | .[0:10] | .[] | {filename, total_compressed_size, num_parts}'Directory tree for a route
grep '"route":"/"' .next/diagnostics/analyze/ndjson/sources.ndjson \
| jq 'select(.parent_id == null)'Related skills
Vercel React Best PracticesAutomatically apply Vercel’s official React and Next.js performance rules during code generation and review.576k29.4kVercel Composition PatternsGenerate and refactor React components that stay maintainable as complexity grows without boolean prop explosion.261k29.4k
ShadcnAdd, compose, search, fix, and style production-grade React components directly from source without leaving their editor.249k120k
Develop UserscriptsCorrectly write, debug, and package userscripts for Tampermonkey and ScriptCat with proper metadata, GM APIs, and runtime decisions.224k72
Minimalist UiGenerate clean, editorial-style web interfaces with warm monochrome palettes, typographic hierarchy, bento grids and flat components that feel premium and utilita201k66.9kVercel React Native SkillsEnsure AI agents generate and refactor React Native code that follows performance best practices without common rendering and list pitfalls.173k29.4kFAQ
What input does this skill expect?
Next.js bundle analyzer output data from a production or analyze build.
What format is produced?
NDJSON for line-by-line programmatic filtering and exploration.
What can I find in the output?
Module sizes, dependency contributions, and candidates for code splitting or removal.
Is Analyze Bundle safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.