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

Third party typescript components not getting parsed

Open
#416 2 comments 28 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
react, typescript
Domain
documentation

Research direction

The issue links styleguidist/react-styleguidist#1508 and names react-docgen-typescript plus react-docgen v5; start by reading that linked report and comparing their handling of third-party component props. Done means props from third-party TypeScript components are parsed and listed on the extended component.

Written by the indexing model from the issue text.

Description

improvement

This is coming from https://github.com/styleguidist/react-styleguidist/issues/1508

Previously with react-docgen-typescript, third party component props are getting parsed and visible with the extended component. But with react-docgen v5, they are not getting listed.

Dominant language
TypeScript
Stars
3.8k
Forks
316
Avg merge
3h 28m
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

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 reactjs/react-docgen

All issues in reactjs/react-docgen

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.