optimize-bundle-size

To reduce Kibana plugin page load bundle size, analyze build metrics and refactor code splitting and module imports. This identifies heavy dependencies and prevents unnecessary increases to package limits.

Kibana CI page-load overages occur when plugin changes exceed the bundle limits defined in packages. Pull requests fail when new features introduce heavy imports or unoptimized code that inflates the bundle beyond acceptable thresholds.

The best way to debug a Kibana plugin bundle size overage is to use profiling and build metrics to analyze the plugin. This identifies the specific modules causing the bloat so you can optimize code splitting and resolve the CI page-load issue.

You can optimize JavaScript bundle size proactively by analyzing module imports and utilizing build metrics to enforce code splitting. This prevents unnecessary increases to the package limits file and avoids CI page-load overages during development.

Yes, the optimize-bundle-size Skill works without external dependencies. It uses built-in scripts and references to analyze Kibana build metrics, manage package limits, and refactor module imports to reduce plugin bundle sizes effectively.