In D15108#416407, @tomek wrote:

According to the docs https://flow.org/en/docs/types/indexed-access/

We have created an ESLint rule that warns on $ElementType and $PropertyType usage and recommends Indexed Access Types instead. It includes an auto-fixer that can handle most cases. You can simply enable this rule on your codebase and autofix all existing issues.

Install eslint-plugin-fb-flow, and add fb-flow to your ESLint plugin list. Then enable the rule in your ESLint config:

'fb-flow/use-indexed-access-type': 1,

Are we doing it in this stack?

No, but we don't need to. The rule was introduced only in order to autofix the issues and I preferred to use search&replace. If we use $ElementType or $PropertyType now, Flow will throw an error, so we don't need additional eslint rule.