Problem statement
Contributors and maintainers currently have limited visibility into the performance characteristics of the browser-based IDE. As Editron grows with more starter templates, AI integrations, collaboration features, and complex UI components, page load times, bundle sizes, and runtime responsiveness can gradually degrade without being immediately noticeable.
Without a centralized performance monitoring system:
Regressions can be introduced unnoticed during feature development.
Contributors cannot easily identify performance bottlenecks before submitting PRs.
Maintainers lack historical performance data to compare releases.
Large dependencies and inefficient rendering patterns may accumulate over time.
This makes it difficult to maintain a fast and responsive development experience for users.
Proposed solution
Introduce a Performance Analytics Dashboard for maintainers and contributors.
The dashboard should:
Collect Lighthouse metrics during CI runs.
Track Core Web Vitals (LCP, CLS, INP, TTFB).
Display bundle size trends across commits and releases.
Highlight performance regressions beyond configurable thresholds.
Provide a visual history of performance scores.
Surface the largest JavaScript bundles and routes.
Generate performance reports as GitHub Action artifacts.
This feature would help contributors detect issues early and enable maintainers to make data-driven optimization decisions.
Alternatives considered
Running Lighthouse manually before releases.
Using external performance-monitoring services.
Reviewing bundle sizes only during code review.
These approaches either require manual effort or do not provide consistent repository-wide performance tracking.
Estimated scope
Small
Primary area
Playground editor
Additional context
Potential implementation areas:
GitHub Actions workflow integration
Lighthouse CI configuration
Next.js bundle analyzer integration
Dashboard page under admin or maintainer tools
Historical report storage using GitHub artifacts or database-backed metrics
Expected benefits:
Early detection of performance regressions
Better contributor awareness
Improved user experience
Long-term maintainability as the project scales
Confirmation
Problem statement
Contributors and maintainers currently have limited visibility into the performance characteristics of the browser-based IDE. As Editron grows with more starter templates, AI integrations, collaboration features, and complex UI components, page load times, bundle sizes, and runtime responsiveness can gradually degrade without being immediately noticeable.
Without a centralized performance monitoring system:
Regressions can be introduced unnoticed during feature development.
Contributors cannot easily identify performance bottlenecks before submitting PRs.
Maintainers lack historical performance data to compare releases.
Large dependencies and inefficient rendering patterns may accumulate over time.
This makes it difficult to maintain a fast and responsive development experience for users.
Proposed solution
Introduce a Performance Analytics Dashboard for maintainers and contributors.
The dashboard should:
Collect Lighthouse metrics during CI runs.
Track Core Web Vitals (LCP, CLS, INP, TTFB).
Display bundle size trends across commits and releases.
Highlight performance regressions beyond configurable thresholds.
Provide a visual history of performance scores.
Surface the largest JavaScript bundles and routes.
Generate performance reports as GitHub Action artifacts.
This feature would help contributors detect issues early and enable maintainers to make data-driven optimization decisions.
Alternatives considered
Running Lighthouse manually before releases.
Using external performance-monitoring services.
Reviewing bundle sizes only during code review.
These approaches either require manual effort or do not provide consistent repository-wide performance tracking.
Estimated scope
Small
Primary area
Playground editor
Additional context
Potential implementation areas:
GitHub Actions workflow integration
Lighthouse CI configuration
Next.js bundle analyzer integration
Dashboard page under admin or maintainer tools
Historical report storage using GitHub artifacts or database-backed metrics
Expected benefits:
Early detection of performance regressions
Better contributor awareness
Improved user experience
Long-term maintainability as the project scales
Confirmation