Blake Embrey

Just commenting to say the generic code looks more like: ``` js var defer = typeof setImmediate === 'function' ? setImmediate : function(fn) { var args = Array.prototype.slice.call(arguments, 1) process.nextTick(function()...

`@types` has no relation to this module, if you want someone in the community to type it you can ask at https://github.com/DefinitelyTyped/DefinitelyTyped which is where `@types` is published from. You...

@origin1tech I do know what you're talking about. DefinitelyTyped is the location you should ask if you want something published to `@types`. The `@types` on NPM has **zero** relation to...

@dougwilson We can't, and we wouldn't want to. Once someone has written a definition, we can add it to the module ourselves and publish to NPM directly (using `typings` in...

@origin1tech You're missing the point. Please re-read my comments. If the goal is "ease of install" we would add them to **this module**, and not @types. That way, as a...

@origin1tech You're incorrect. That approach is relevant **only** for third-party typings (E.g. those from Typings/DefinitelyTyped). Modules themselves can publish their own type definitions, and that has been the preferred approach...

@origin1tech You can read up on how `exclude` works in the TypeScript handbook, but it won't break that. `exclude` is there to ignore "entry-points" of the project. If something requires...

Here's a response by Daniel on the same article you posted. 

If you've used Typings before, `@types` is basically doing the same resolution, filling that gap in tooling - just all natively within the NPM and TypeScript ecosystems now instead of...

But why? Imagine you have a native TypeScript project. It wouldn't make any sense to make the author's life more complicated. Just like here, if the author's are willing to...