Upgrading typescript-config module version to esnext

[mateoguzmana]

Summary:

Fixes #45810

Upgrading typescript-config module version from es2015 to esnext, in order to support dynamic imports.

Changelog:

[GENERAL] [CHANGED] - Upgrading typescript-config module version to esnext

Test Plan:

Create a new React Native project:

npx @react-native-community/cli@latest init AwesomeProject

Copy the changes in the reproducer from the linked issue and add a lazy import:

const LazyAssetExample = React.lazy(() => import('./components/AssetExample'));

See the error when running yarn tsc:

---

To fix the error, apply the following patch:

diff --git a/node_modules/@react-native/typescript-config/tsconfig.json b/node_modules/@react-native/typescript-config/tsconfig.json
index d5e1bce..51f54c1 100644
--- a/node_modules/@react-native/typescript-config/tsconfig.json
+++ b/node_modules/@react-native/typescript-config/tsconfig.json
@@ -3,7 +3,7 @@
     "display": "React Native",
     "compilerOptions": {
       "target": "esnext",
-      "module": "es2015",
+      "module": "esnext",
       "types": ["react-native", "jest"],
       "lib": [
         "es2019",

Verify it is fix by running yarn tsc again

[NickGerleman]

@huntie, to sanity check, is this supported by Metro out of the box?

An aside, we're probably overdue for an update on ES lib support in the config as well (last time it was updated was a couple years ago, and I wouldn't be surprised if Hermes has added support for more things).

[NickGerleman]

Looks like yes https://metrobundler.dev/docs/module-api/#import-dynamic-import

[facebook-github-bot]

@NickGerleman has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[facebook-github-bot]

@NickGerleman merged this pull request in 5370347.

[react-native-bot]

This pull request was successfully merged by @mateoguzmana in 5370347

^{When will my fix make it into a release? | How to file a pick request?}