Specify differences (pros and cons) with typings

Open nicojs opened this issue 9 years ago • 2 comments

Right now, there is no section in the readme.md which explains the difference with typings. This is a big question for users. Could you please tell us? I think the 'no worries' suggests that we have worries. Please explain that as well.

Apr 05 '16 06:04 nicojs

haha, you beat me to it.

Apr 05 '16 17:04 samvloeberghs

IMHO, what typings is doing is letting a parallel package manager to handle the type definitions.

This causes more dependencies for your project, another cli command line tool that you need to learn and additional infrastructure for the guys maintaining that.

I think npm only approach is better. The idea of using npm is not old and was suggested even in DefinitelyTyped repository. Sadly I don't see any hype around it and I actually can't understand why.

There is a bit explanation here :

https://github.com/typings/typings/issues/223

May 11 '16 16:05 drinchev