tsd should be discouraged. dtslint should not be discouraged

[Ore4444]

No description provided.

[slikts]

The dtslint readme actually points to tsd:

Just looking for ExpectType and ExpectError? Use tsd instead.

tsd issue comparing it it to dtslint which brings up a number of points in favor of tsd.

Comment by a dtslint developer:

dtslint is primarily for use as Definitely Typed infrastructure (or if you're building a DT-like type repository). If you are writing unit tests for types you should be using tsd instead of dtslint.

Another one:

For lighter-weight checks, try tsd, which works within the type system, giving you a library you can import into existing unit tests. It's also more usable and gives you feedback as you type.

tsd is a newer tool, but is focused on developer experience and is being improved, like by adding strict type assertions, so I think it's reasonable to recommend it over dtslint.

[Ore4444]

Thabks for the detailed answer! I see where i got it wrong