tsd property in package.json instead of tsd.json?

[rhbecker]

Hey, I'm new-ish to using tsd (arrived here via ms visual studio code), so please excuse the likely naïveté of this question ...

Have you considered supporting a tsd property within package.json as an alternative to a separate tsd.json file? I doubt I'm the only one who likes to minimize the sprawl of "meta" config files, and one less file at the root of my projects is appealing.

FWIW, eslint has adopted this approach.

I tried poking around existing issues to see if this has been raised:

1. #200 seems to have a similar motivation
2. #208 addresses some sort of support within package.json, but as far as I can tell, it's addressing a distinct issue?