Metro+TS: support additional package.json fields when resolving a module to a file

[afoxman]

What happened?

In @rnx-kit/typescript-react-native-resolver, the function resolveModule (src/resolve.ts) looks for "default" entry point files in package.json -- fields like "main", "types", and "typings".

Repos using newer or custom tech may have other custom fields in their package.json files which refer to additional entry points. For example, Apollo uses the "module" field to refer to the main ES6 module in the package.

This should be an optional configuration parameter which defaults to no additional fields.

Affected Package

@rnx-kit/typescript-react-native-resolver

Version

Which platforms are you seeing this issue on?

• Android
• iOS
• macOS
• Windows

System Information

N/A

Steps to Reproduce

N/A

Code of Conduct

• I agree to follow this project's Code of Conduct

[afoxman]

TypeScript doesn't support this type of extension, though they do have a more sophisticated resolver. With microsoft/TypeScript#48189 being imminently accepted into TS main, I will be deprecating typescript-react-native-resolver.