gea

This skill provides a dedicated interface for managing the js-framework-benchmark process within the Gea repository. It is designed for developers and performance engineers who need to monitor framework overhead, compare Gea against other frameworks like Solid, Svelte, Vue, and React, and maintain the accuracy of the local benchmark report. By utilizing a curated set of configured frameworks from benchmark-report.config.json, the skill automates the regeneration of result data and ensures the HTML dashboard is always up-to-date for local analysis.

• Executes repo-specific benchmark workflows using the update-js-framework-benchmark-report.mjs wrapper.

• Regenerates webdriver-ts-results/src/results.ts and rebuilds the dist folder to reflect the latest performance data.

• Supports filtered benchmarking, allowing users to run specific frameworks (e.g., keyed/gea) or particular test categories (e.g., 03_update10th1k_x16) to isolate performance regressions.

• Provides immediate access to the local development server at http://localhost:8080/webdriver-ts-results/dist/index.html after any report update.

• Distinguishes between local curated runs and full upstream js-framework-benchmark matrix requests to avoid unnecessary system load.

• To perform a standard report refresh, use commands like "update the report" or "refresh the HTML".

• Use "run all frameworks" to execute the full set defined in your configuration file.

• Always ensure the benchmark server is active prior to regeneration, as the tool queries the /ls endpoint for result data.

• If a custom one-off report is generated with specific flags, remember to trigger a standard refresh afterward to restore the default comparison view.

• Avoid running broad upstream benchmarks unless explicitly requested, as the local wrapper is optimized for the project's specific comparison needs.