Tsd: Deprecate TSD

:+1:

for refernces to upgrade from tsd

webpack+typescript
https://github.com/angular/universal-starter/commit/cfb7b52b12e1da9de7ee7c2a452e7636c93aaa09

gulpjs+typescript
https://github.com/angular/answers-app/pull/27/files

gulpjs with typescript
https://gist.github.com/gdi2290/e544407980e261acc172

commands

$ npm uninstall tsd
$ rm -rf typings
$ npm install typings
$ typings init --upgrade
$ rm tsd.json
$ typings install

Just a small addition to @gdi2290 migration steps regarding something that just happened to me.
If someone follows it and end up with hundreds of TS2300: duplicate indetifier ... during compiling, the solution is here https://www.npmjs.com/package/typings#maindts-and-browserdts

How do you do tsd link with typings?

How do you do tsd link with typings?

You don't. TSD link is flawed and not really a solid long-term solution - as it relies on ambient modules, causes duplicate identifiers and generally forces users to re-install sub-dependencies. Assuming you want the exact same thing, you can do typings install npm:<library>/<path-to-d-ts> --ambient. Most likely, you want a different solution where sub-dependencies are being handled properly. In that case, publish your typings.json file with your library and do typings install npm:<library> --save - the dependencies in <library>/typings.json will resolve.

Ran into an issue installing typings from another repository. Created an new issue: https://github.com/typings/typings/issues/133

Just wondering what the vision/intent here is for DefinitelyTyped/tsd vs Typings? I get that Typings is decentralised and that it can talk to DefinitelyTyped, but I also know that Typings has repos for some popular projects as well... hence my question.

Wouldn't it make sense to mandate all typedefs be forced centralized in npm package installations instead of replicating half the efrastructure inside our local projects ?

• no tsd
• no typings
• no replication of effort
• no repeat dependency footprints...

JSPM is alarmingly a case in point

NPM already has the fittings to support and process this.

Is anyone even theorizing the impact of transient dependencies ?

I wouldn't send my kid to a daycare, which subs out the task to another daycare somewhere else... something is eventually going to disconnect... let alone a single transient dependency roaming thru the ecosystem.

@nhhockeyplayer ideally that would be the case but for this to happen every author would need to include and maintain type definitions.

Related

• https://github.com/moment/moment/pull/2916
• https://github.com/pwnall/node-xhr2/pull/20

For Angular 2 we can assume every ng2 module will include type definitions but for the other modules that will likely not be the case. So there will be a community (ng2) who will benefit more by ensuring every module in it's ecosystem includes type definitions (the ideal case).

@blakeembrey sorry for bumping this issue. Just noticed the deprecation notice added to the readme here on github is not on npm which could lead to people still using it without initial knowledge that the package is deprecated. It's probably because there was no new release since the package got deprecated.

If you do NPM install, it says it.

Edit: But I'll check it out and release a new version.

Cool, then it's fine 👍

could you add a deprecation notice to the npm page?
Makes it easier for returners to figure out about typings.

It would be cool to ship complete and finished version of typings first and then deprecate tsd because right now typings only makes things harder and confusing with this mess with multiple repos IMO. 😠

There are four issues on this issues page now dating back months, pointing out that tsd no longer functions for installing basic packages such as jquery or react. Deprecating or halting development is one thing, but it appears tsd has actually been shut down (?). This is a real problem— especially since there seems to have been no kind of explicit announcement service was outright discontinuing— since tsd is the kind of tool which could be part of automated deployment. I just had a web service kill itself because its automated deployment runs tsd, which no longer works.

It says it is deprecated on install for over a year now. Since TSD is based on GitHub, it all still works perfectly fine. What you'd be seeing is DefinitelyTyped changes. The TSD architecture can not handle the changes, and the move was a decision from TypeScript to support NPM @types.