Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Debugging data collection affects meta-frameworks differently

Open
  • Is something wrong?
#574 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
javascript, typescript
Domain
performance, testing-qa

Research direction

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.

Written by the indexing model from the issue text.

Description

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

Dominant language
TypeScript
Stars
42
Forks
16
Avg merge
13h 41m
Merged PRs (30d)
144

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from e18e/framework-tracker

All issues in e18e/framework-tracker

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.