Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Show error bars on timing metrics

Abierto
  • ¿Algo no está bien?
#633 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
data-visualization, frontend

Línea de trabajo

Start by finding where the timing JSON is loaded and where the charts and tables render these metrics, then check the install and FCP entries for the standardDeviation(Ms) field and raw samples. Error bars on charts and ± in tables should first cover install and paint metrics, which already have spread data. Recording spread for SSR throughput and load is a separate benchmark change, and the issue does not say how error bars should look, so confirm that with maintainers before you start.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

discussion

The timing metrics that are measured by framework-tracker itself (install, cold/warm build, dev server start, FP/FCP, interaction breakdown, SSR throughput/load latency) are noisy by nature. The site currently shows one number per framework, so small differences look meaningful even when they're within noise. Showing a single value without its spread isn't really as honest as it should.

A couple of examples from the current Next.js data:

  • install time: 5744 ms avg, std dev 1688 ms (samples: 2729 to 6631)
  • client-side FCP: 405 ms avg, std dev 141 ms

Most of this data is already collected: standardDeviation(Ms) and raw samples are in the JSON for install, builds, dev server start, and the CSR/SSR paint and interaction tests. It's just not displayed anywhere.

Proposal

  • Add error bars to charts (and ± in tables) for every timing metric framework-tracker measures itself
  • Start recording spread for the ones that don't have it yet (SSR throughput, SSR load)
  • 3rd-party data (HTTP Archive CWV): I don't know what spread info the source provides, but if it's available, show it there too
  • Exact counts and sizes (dependency counts, node_modules size, …) don't need any of this

Related: #407

Lenguaje dominante
TypeScript
Estrellas
42
Forks
16
Merge medio
13 h 56 min
PR fusionados (30 d)
141

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de e18e/framework-tracker

Todos los issues de e18e/framework-tracker

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.