react-component / react-component/tree
There shouldn't be any issues, it's probably freaking out because it's opening a command prompt. To use the debug patch just put it in your MV folder beside your normal install
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 490
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 5
Description
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The only artifact named is the linked debug-ptach.zip release and its reference to an MV folder. Start by checking whether that archive and the command-prompt behavior belong to react-component/tree; no source file or test is identified. Done would require a confirmed reproduction and a concrete change target in this repository.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 1/100