Migration path from current DefinitelyTyped RN typings about flow2dts HOT 6 OPEN

We should consider providing a codemod that users can apply to their codebase to upgrade some/all of these.

from flow2dts.

• TypeScript does not have a build in way to deal with different files for different platforms.

  • How can we offer distinctive sets of typings for iOS and Android (eg @types/react-native-ios, @types/react-native-android) and let the user configure them for their project?

Perhaps we can find a way to alias @types/react-native-ios to @types/react-native in tsconfig.json, that way people can have different configs per platform and importing from the react-native namespace should still work.

TS doesn't need to resolve specific extensions, as currently we’re generating distinctive sets per platform and dropping the platform file extension.

• And can other DT packages that depend on RN use this too?

Additionally we could update the actual @types/react-native package to import and re-export the top-level exports of both @types/react-native-ios and @types/react-native-android so they can possibly depend on them in a platform independent manner? Unsure how feasible this is.

from flow2dts.

Could it help if we were able to release DT packages with version suffix? E.g. 0.64.0-ios and 0.64.0-android.

from flow2dts.

Also need to decide what to do with fallout in all DT packages that depend on the RN typings, assuming there will be.

from flow2dts.

One solution to providing the packages using alternate names would be to use declare module "react-native/..." {} for each module, e.g. see https://github.com/DefinitelyTyped/DefinitelyTyped/pull/49914/files#diff-8b9d499e69407ece17612b602d5355d8a1c8b2e5fdb6628e288638aab682ef29R7

from flow2dts.

Looks like TypeScript people are working on supporting this scenario

from flow2dts.