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

Idea: use `trace` to enter the debugger for a component

Open
#19 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
devtools, frontend

Research direction

Start by reviewing the existing visual observer-component selection and debugger entry points in the Chrome extension, then compare the referenced tracing behavior in the newest MobX version. Done means selecting a component and entering the debugger when that component is required to rerender.

Written by the indexing model from the issue text.

Description

enhancement

Hey Andy!

A cool idea: What if you could visually select an observer component, and then trace its reaction automatically (see newest mobx version)? I think it is pretty cool that you can click a component and then enter the debugger as soon as it is required to rerender.

Dominant language
JavaScript
Stars
503
Forks
34
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 mobxjs/mobx-devtools

All issues in mobxjs/mobx-devtools

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.