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

Debugging data collection affects meta-frameworks differently

Abierto
  • ¿Algo no está bien?
#574 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
35/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
javascript, typescript
Área
performance, testing-qa

Línea de trabajo

Start by locating the Lighthouse configuration and benchmark entry points used for CSR and SSR measurements. Compare runs with Stack Capture, Precise JavaScript coverage, and debugger async-stack tracking enabled and disabled, then determine whether a consistent configuration or documented limitation is needed. Done means framework comparisons are not unevenly affected by these debugging options.

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

Descripción

discussion

Lighthouse enabled a bunch of debugging tools, that can be very useful to precisely track down which piece of code is responsible for what, but it affects different meta-frameworks differently.

The main options I found that contribute to this are:

  • Stack Capture
  • Precise JavaScript coverage
  • Debugger async-stack tracking

"stack capture" is the most impactful as far as i can tell. For example when i tried disabling it on a task i was benchmarking i got this:

Measurement CSR SSR
Late task, default Lighthouse 44.1 ms 44.1 ms
Same task, stack capture disabled 4.6 ms 5.2 ms

But the main problem is that it doesn't affect all meta-frameworks the same way. For "stack capture" for example its impact depends basically on the number of function calls and their depth. So the comparison across frameworks becomes less fair.

FWIW in the next version of TanStack Start the INP measurements are not impacted by any of these features any more than the other frameworks (they seem to all be pretty much within noise of each other). But these options could still impact future measurements unequally (like if a "navigation" measurement is added later, this will probably show up).

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

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.