Seperate definition for all experimental web features

[basarat]

We can do that if there is community interest.

It would be simplest to just reference the definitions from their current locations in a new folder (lib).

The current files found:

• WebRTC : https://github.com/borisyankov/DefinitelyTyped/tree/master/webrtc
• WebCrypto: https://github.com/borisyankov/DefinitelyTyped/tree/master/webcrypto
• Promise Spec : https://github.com/borisyankov/DefinitelyTyped/blob/master/promises-a-plus/promises-a-plus.d.ts combined with an ES6 only definition

Updated : new name lib

[basarat]

#2498: Desire for Number.isNaN : https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/isNaN which actually cannot be done (Vote : https://typescript.codeplex.com/workitem/1085)

[Bartvds]

👍

And I sometimes feel there is room for a shared library kinda thing, like the Thenables from promise-a.

Maybe like a ./lib? A thing is a thing and using 'experimental' is messy as many of these currently experimentals will stablise at some point so we might as well put them in the right spot (otherwise what we do? removing stuff is bad).

[sedwards2009]

I'm already (privately) maintaining my own copy of lib.d.ts with a number of modifications to support bleeding edge Chrome and node-webkit APIs.

Major changes include:

• HTMLElement and subinterfaces are now classes which can be subclassed to support custom elements.
• Shadow DOM related types and methods.
• New CustomEvent constructor.

I've got code to do the HTMLElement transform and merge in the other changes. I would be happy to share my lib.d.ts and my code to build it.

TypeScript's issue tracker has plenty of lib.d.ts related issues and it looks like they intend to tackle them, but this will take a while. In the mean time an alternate lib.d.ts (or collection of alternate lib.d.ts for different environments) is needed otherwise some of us can't continue with our own projects.

Another question is whether MS are interested in supporting APIs (and non-standard APIs) which only exist in other browsers. From what I can gather, lib.d.ts is currently derived from IE's API description files.

[basarat]

Another question is whether MS are interested in supporting APIs (and non-standard APIs) which only exist in other browsers.

No.

lib.d.ts is currently derived from IE's API description files.

Yes, but they do welcome manual fixes when they make sense e.g. microsoft/TypeScript#337