Dmitry

Hmm, regarding being unable to compile and run, I am not sure why -- it works for me on a clean checkout. I run `npm install`, then `npm run test`....

Actually, I think that comment is a red herring here (it's about circular data, while the actual problem here is circular definitions). Circular definitions *should* be handled, and the fact...

Do you mean that [ts-interface-builder](https://github.com/gristlabs/ts-interface-builder) should have this flag? It already has a `--format` flag, to output `ts` or `js:esm` or `js:cjs` code (differing mainly in import and export syntax)....

Happy to have a PR adding tslint directive. Changing the variable name seems trickier -- now it matches the name of the interface it represents. We could add a "ti"...

To be honest, I've been working with major overrides of the theme that have diverged in a big way, in particular because of issues in getting pages indexed by search...

Yes, closing. Thanks for the reminder.

Did you figure this out? If there is a difference between dev and prod, that seems likely a build-related issue. From your example, I can't tell what `todoUserTI` and `userProfileTI`...

It's possible already! Something like this should work: ``` import {assert} from "chai"; import {BasicType, createCheckers} from ".."; import * as t from ".."; // tslint:disable:object-literal-key-quotes export type Iso8601Date =...

Yup, this looks like it should work!

See my response here: https://github.com/gristlabs/ts-interface-checker/issues/37#issuecomment-770279185 As I said there, proper support for generics is hard, and I don't think I can make the time to make it happen. But if...