Support TypeScript 2.0

[use-strict]

TypeScript 2.0 beta is up on npm. @vvakame, @basarat , I'll want to update some typings for jQuery but I need tsc 2.0 support first. Do you know what exactly has to be done for this to work?

A big problem also is about breaking changes. Function 'this' types, in conjunction with 'noImplicitThis', will lead to definitions that will be incompatible with older compiler versions. There are probably other backwards-incompatible changes, like patterns in module declarations.

[mhegazy]

The TS-2.0 specific declarations are in types-2.0 branch. feel free to send PRs against that branch. also worth noting that this branch is where the @types packages get published from.

We intend to merge the types-2.0 branch into master a few weeks after the final TS 2.0 release.

[use-strict]

Great, thanks. I'll have a go at it tomorrow.

[use-strict]

Looks like that branch is using tsc 1.8 as well. Maybe I'm doing something wrong. I ran npm install followed by npm test.

[use-strict]

@mhegazy , looks like the npm-shrinkwrap.json file is not consistent with package.json. It should be regenerated.

[use-strict]

Removed devDependencies from shrinkwrap. #10092

[jleider]

I see the use-strict-jquery-ts2-this branch but those updates have not been merged into the types-2.0 branch. This would be great to get merged into the types-2.0 branch.

[e-cloud]

@mhegazy , there have been more than a few weeks from July. Is there a clear plan to merge types 2.0 into master?

[zakdances]

I'm unclear on this too - at this time, which branch should we be PR'ing?

[screendriver]

Quote from the docs

New work should generally be done on the types-2.0 branch. If you want your changes to be available to typings users, then you may edit master instead.

[vvakame]

It landed to master branch already. 😉

[e-cloud]

So, should we now all commit PR on master rather than types-2.0?

[vvakame]

@e-cloud I understand so. @DefinitelyTyped/contributors is this rights?