Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Give a better error message when using a custom tsconfig with an invalid include path #134

Closed
teddybradford opened this issue Oct 1, 2018 · 0 comments · Fixed by #156
Closed

Give a better error message when using a custom tsconfig with an invalid include path #134

teddybradford opened this issue Oct 1, 2018 · 0 comments · Fixed by #156

Comments

@teddybradford
Copy link

teddybradford commented Oct 1, 2018 •
edited
Loading

When using withCustomConfig() with a tsconfig.json file that has an invalid include path, such as a relative parent path (include: ["../somedir"]), the styleguidist server script prints "undefined" and then exits immediately when run.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: better error message for non existing custom tsconfig pvasek/react-docgen-typescript
1 participant
@teddybradford