[pkg]: "postinstall": "tsd install"

[calebboyd]

@mhevery, this statement breaks npm install for those who do not have tsd installed globally.

I'm not too sure how you'd like to alter that installation

[cloudlena]

I agree. As a person using the newer typings instead of tsd, this breaks my installation.

[cebor]

same here

[psi-4ward]

+1

for now i npm i tsd

[cebor]

strange thing is, that tsd is already added to devDeps

[calebboyd]

@cebor, the problem is that dev dependencies are not installed for consumers

[cebor]

yes you are right, so i think its better to remove the postinstall and document the tsd install as a manual step for contributors

[TheTedAdams]

+1 that this just broke our build.

postinstall tries to run tsd install on anyone installing this package from npm, which I don't think is what you were trying to do.

With tsd in devDependencies there is no guarantee tsd has been installed on the consumer. As a consumer I would also much rather postinstall was just removed, rather than adding a dependency on a successful tsd install. We have had tsd fail with API rate limiting so much that we have removed it from our build process and just added our typings folders to git...

[PatrickJS]

+1 postinstall breaks angular2 beta.3 unless tsd is installed as a dependency

[Kikketer]

+1 Beta.3 fixes issues I have with multiple of the same components, but the dependency of installing tsd breaks my build on a build server. Moving back to beta.2 until this can be fixed.

[jrisk]

same here, npm install tsd -g did fix the ERR messages atleast