verify-bundle-size

Verify Vite code splitting and bundle size against performance benchmarks.

Updated Dec 23, 2025
One-click install
npx skills add https://github.com/BIGSHOL/ijw-Calander --skill verify-bundle-size
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-bundle-size
Source: https://github.com/BIGSHOL/ijw-Calander/tree/main/.claude/skills/verify-bundle-size
Command: npx skills add https://github.com/BIGSHOL/ijw-Calander --skill verify-bundle-size

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure your application's JavaScript bundle size is optimized by verifying code splitting effectiveness and detecting large dependencies.

Core Features & Use Cases

  • Code Splitting Verification: Confirms that React.lazy imports are correctly creating separate JavaScript chunks.
  • Large Dependency Detection: Identifies if large libraries are being directly imported, potentially increasing bundle size.
  • Build Success Check: Ensures the TypeScript build process completes without errors.
  • Use Case: After adding a new charting library or refactoring component loading, run this Skill to confirm that code splitting is working as expected and the main bundle remains lean.

Quick Start

Run the verify-bundle-size skill to check your application's build optimization.

Frequently Asked Questions about verify-bundle-size

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code splitting effectiveness in a Vite application?

To verify code splitting effectiveness in Vite, analyze generated JavaScript chunks to confirm React.lazy imports correctly create separate bundles and identify large directly imported dependencies.

Why does my main bundle size increase after adding a new library?

Your main bundle size increases when large libraries are directly imported instead of lazy loaded. Detect these large dependencies and ensure they are correctly split into separate JavaScript chunks to keep the main bundle lean.

Can I check if React.lazy imports are creating separate JavaScript chunks?

Yes, you can check if React.lazy imports are creating separate JavaScript chunks by analyzing the generated build output to verify code splitting effectiveness and confirm the main bundle remains optimized.

How do I ensure TypeScript compilation success when optimizing bundle size?

Ensure TypeScript compilation success when optimizing bundle size by running a build process check that verifies the compilation completes without errors before analyzing generated JavaScript chunks for performance benchmarks.

What is the best way to detect large dependencies affecting web app performance?

The best way to detect large dependencies affecting web app performance is to analyze generated JavaScript chunks against performance benchmarks, identifying large libraries that are directly imported and failing to split into separate bundles.