Skip to content
This repository has been archived by the owner on Dec 18, 2018. It is now read-only.

Specify differences (pros and cons) with typings #4

Open
nicojs opened this issue Apr 5, 2016 · 2 comments
Open

Specify differences (pros and cons) with typings #4

nicojs opened this issue Apr 5, 2016 · 2 comments

Comments

@nicojs
Copy link

nicojs commented Apr 5, 2016

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.

@samvloeberghs
Copy link

haha, you beat me to it.

@drinchev
Copy link

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 :

typings/typings#223

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants