-
Notifications
You must be signed in to change notification settings - Fork 710
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
TypeDoc out of memory error in 0.15 #1150
Comments
This is happening because we call TypeScript's |
It looks like fixing this specific case just requires adding a new type converter for types with kind |
Well, believe it or not, those same types are powering ramda. They are recursive types that are crafted not to overflow, the docs were generating properly before I started forcing distribution. In any case, it's my bad, I was distributing a type that ended in a redistribution loop. So this is not a bug, it's my mistake and typedoc is working correctly 🎉 |
TypeDoc should still handle it correctly, so it is a bug I'd like to fix :) I have a fix for the JSON output, I just also need to verify that it works as expected when generating html. The recursive types won't overflow - so long as they are passed a type. The issue here is TypeScript assumes they aren't recursive and can be fully expanded without a value. |
closes #1150 closes #831 * Added test for conditional types. i.e. `X extends A ? B : C` Currently results in { "type": "unknown", "name": "X extends A ? B : C" } See #831 * Add support for conditional type. * add a test for infer * feat: Add support for indexed access types Co-authored-by: Adrian Leonhard <[email protected]>
Fix has been merged, I should get a release out later today :) |
Hi @Gerrit0, I'm also getting the same error on my repo
https://github.com/pirix-gh/ts-toolbelt
npm run build:docs
This happens since my last update, where I made type distribution a default. So I suspect that typedoc tries to unfold types too much. I'd be nice if it could preserve the type "as it is" in the code.
Originally posted by @pirix-gh in #835 (comment)
The text was updated successfully, but these errors were encountered: