Closed johnnyreilly closed 8 years ago
Would a compiler option that restricts applying these rules to external projects be something you might consider
I believe the newly introduced skipLibCheck
option does exactly that :rose:
Thanks @basarat! - I hadn't heard of that option; is that part of 1.8 or is it slated for 2.0?
I see it - 2.0. thanks! https://github.com/Microsoft/TypeScript/wiki/Roadmap
Will close as it looks like this is resolved by https://github.com/Microsoft/TypeScript/pull/8735
@johnnyreilly :arrow_right_hook: I've made an alm
release 0.0.87
that supports this option :rose:
I would expect nothing less :smile: :tulip:
I was trying out the new angular ui router which has been ported to TypeScript and ships with definitions in the box. However, it looks like the compiler rules for my own project are being applied to the angular ui router project as well.
TypeScript Version:
1.8.10
Code
Using this
tsconfig.json
:Expected behavior:
StateProvider
is pulled in and can be used. No errors.Actual behavior: It errors with:
All of these are external to my own project; I wouldn't have expected that this would be an issue. As it happens the good folks of angular ui router are planning to remedy this. But if, for whatever reason, they didn't then I'd either have to change the choices made in my own project to align with theirs or not use their project. Neither of those is great.
Would a compiler option that restricts applying these rules to external projects be something you might consider? Whilst packages that ship with typings in the box is at the moment relatively niche I can imagine that changing massively over time.