Typescript@next removed/renamed TypeVariable

[ajafff]

Typescript@next removed/renamed TypeVariable

[ajafff]

Thank you for the report. Unfortunately there's no easy way to fix this for you.
If I change the public API to be compatible with the upcoming [email protected], it will break everyone else who's still using the latest release 2.7.2

I could however publish a new version as tsutils@next until [email protected] is released.

[ajafff]

in the meantime you could set skipLibCheck: true in your compilerOptions.

[deregtd]

Doing an @next would be awesome. I had to pull in tslint@next as well to fix some other issues with our lint rules, so it looks like in 2.8 they're changing some stuff that everyone's getting ready for. :)

[ajafff]

I'll work on this today and keep you posted here.
I'm a bit puzzled about the tslint@next thing, though ... There was no activity at all in the TSLint repo since the last stable release. tslint@next is v5.0.0-dev which is pretty old to say the least.

[deregtd]

Oh right in the end I went up to 5.9.1 + tslint-microsoft-contrib 5.0.3 and that fixed the actual problem. I tried @next and that fixed one problem (compared to the version I was at), then had to bump again to 5.9.1 to get rid of the last of the issues. Ignore me on that. :)

[ajafff]

@deregtd I actually found a way to make this fix backwards compatible. I just published v2.21.2 which compiles fine with typescript@next

[deregtd]

Works great, thanks so much for the quick turnaround!