Pete Gonzalez

> Providing an explicit typedef solves the underlying instability issue. (BTW I thought your ESLint rules require explicit type declarations?) That said, if the compiler's output depends non-deterministically on the...

To clarify a bit: Since there are many equivalent ways to infer a type, it's unsurprising that a type expression might shuffle around a bit due to modifications of its...

> The types are equivalent and we have never instructed anyone to take a dependency on the text representation of a union type, nor would we. @RyanCavanaugh Then we need...

Does this only happen with inferred types? Will explicitly declared types always get emitted consistently?

> - Union types are printed in an arbitrary order > - Properties in an inferred object type may be printed in an arbitrary order For this, it sounds pretty...

Possible solutions: - The simplest complete solution is for `@rushstack/eslint-config` to warn about usage of inferred types. We already do that. - It would be nice for API Extractor itself...