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

Unable to see Initial State in MST

Open
#30 2 comments 26 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
devtools

Research direction

Start by reproducing the empty Initial State with mobx-devtools-mst 0.9.14 and the shown makeInspectable call after store creation. Trace the makeInspectable entry point and compare how patches and the initial state are captured; done means the initialized MST store appears in Initial State while patches still work.

Written by the indexing model from the issue text.

Description

Hi, I'm using the mobx-devtools-mst package and I can't seem to be able to capture the Initial State. I'm able to see the patches, but the initial state always shows up empty even though I'm calling makeInspectable after I've initialized my main store.

Currently using:
mobx-devtools-mst: 0.9.14
mobx: 4.2.0
mobx-state-tree: 2.0.4
mobx-react: 5.0

  {
// some props to initialize state
  },
  {
// some objects for dependency injection
  },
));

makeInspectable(myStore);```
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.