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

noImplicitAny #2

Closed
altano opened this issue Feb 3, 2015 · 1 comment
Closed

noImplicitAny #2

altano opened this issue Feb 3, 2015 · 1 comment

Comments

@altano
Copy link

altano commented Feb 3, 2015

I would like to use --no-implicit-any, can you expose this as an option?

Ideally, you would allow passing through options the loader doesn't know about to Typescript, so one wouldn't need to make such requests in the future, if possible?

jbrantly added a commit that referenced this issue Feb 3, 2015
@jbrantly
Copy link
Member

jbrantly commented Feb 3, 2015

I've added this in v0.2.3 and published to npm.

Regarding pass-through options, it's a neat idea. It could be kind of crappy if someone was using an undocumented option in one way and then we added first class support for the option in another way and it broke.

FWIW here's the list of available options as of now: https://github.com/Microsoft/TypeScript/blob/9f49a1637a1afc1f7e0953a5748e5088e91dc777/bin/typescript.d.ts#L1127

I don't think it will be unreasonable to just add first class support for the options which make sense in the context of webpack. That said I'm not completely opposed to the idea so perhaps if it becomes an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants