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.

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

noLib option #31

Closed
JeroMiya opened this issue Sep 13, 2014 · 2 comments
Closed

noLib option #31

JeroMiya opened this issue Sep 13, 2014 · 2 comments
Labels
no bug This is expected behavior

Comments

@JeroMiya
Copy link

I want to pass the -noLib option to the typescript compiler for the typedoc build. I use noLib when writing TypeScript for QtScript environments (I have a modified lib.d.ts).

My current workaround is to just overwrite the lib.d.ts for the typescript node module that typedoc transiently depends on.

@sebastian-lenz
Copy link
Member

Actually the -noLib argument should be support, it's read right here and passed on to the compiler. But I have to admit that I've not used/testes this option so far. Do you run TypeDoc from the command line or are you using Grunt/Gulp? Could you provide some kind of test/use case?

@sebastian-lenz sebastian-lenz added the bug Functionality does not match expectation label Sep 20, 2014
@sebastian-lenz
Copy link
Member

Just did a quick test and appended --noLib to the command line, the TypeScript seems to be invoked correctly without the default library definitions.

If I did get something wrong feel free to reopen this issue.

@sebastian-lenz sebastian-lenz added no bug This is expected behavior and removed bug Functionality does not match expectation labels Oct 3, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no bug This is expected behavior
Projects
None yet
Development

No branches or pull requests

2 participants