-
-
Notifications
You must be signed in to change notification settings - Fork 738
Missing documentation with library mode #1380
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.
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
Comments
Pulling this into its own issue to avoid duplicate discussion in the tracking issue. Could you link to a repo which reproduces this issue? I took a quick look at the code where I'd expect the bug to show up, and both places look correct. |
Hi, i have created a similar minimal setup. Thanks in advance. |
I can't seem to reproduce this... I pulled down your repo, installed, ran
(The changed file is package-lock.json - my version of npm added the package name, no other changes) Then, when opening up the documentation, I see this: |
i see you marked this issue as bug.. but after reading your comment.. i m bit confused whether it is bug or i have some kind of dependency issue in my setup.. |
I marked it as a bug because I noticed it didn't have any labels, and needed one to be easier to find. I suspect it's an issue with your setup, and not actually a bug though. |
i got it working with typedoc@next
|
Hmmm... I wonder if this is the same bug as #1382 then, will be looking into it this weekend, and most likely fixing on the |
This is fixed + released in |
bug still kindof happens in 0.20.1 - tsx files are there, but jsdoc are ignored |
in our typescript library repo, we are experimenting with typedoc to generate api documentation.
as typedoc@next, i could do mode="library", which i am guessing is a best mode for us as its a web library.
we have both .ts and .tsx files that exposes modules and react-components to our users.
when i do :
mode="library", .tsx files are ignored.
mode="modules" those are parsed and .tsx components are documented.
note : i'm not sure whether it's a bug or not.
my current ts config
_Originally posted by @Manish3323 in #1364 (comment)
The text was updated successfully, but these errors were encountered: