Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Debugging data collection affects meta-frameworks differently

Aperta
  • Qualcosa non va?
#574 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
javascript, typescript
Ambito
performance, testing-qa

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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).

Lingua principale
TypeScript
Stelle
42
Fork
16
Merge medio
13h 56m
PR unite (30g)
141

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di e18e/framework-tracker

Tutte le issue di e18e/framework-tracker

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.