I think this is kind of a no-brainer, if your project is already based on TypeScript. Not just for configuration, but for things like test fixture data, and ev

I think this is kind of a no-brainer, if your project is already based on TypeScript. Not just for configuration, but for things like test fixture data, and even data assets like i18n translations, or basically anything that projects might commonly use JSON for, internally. It's just so much easier to create, edit, manage, and deal with in TypeScript. But it is hard to imagine TypeScript-as-config taking root in projects that don't already use TypeScript.