[typescript] Create tsconfig.next.json

[marklawlor]

Why

React Contributors discord request

This the first step of many upgrade Expo's SDK to the latest TypeScript and align our tsconfig.json with the recommended settings.

• Extended from @tsconfig/react-native
• @tsconfig/react-native enables strict: true so the partial strict options were removed
• Add noUnusedLocals
• Remove inlineSource, I don't believe this is needed with the new debugger.
• Remove types override. Where we using"jest-require"? Modules that do not run on device should override this setting
• Remove lib override. Modules that do not run on device (or in multiple environments) should override this setting
• Modules are compiled by default (build folder output). Modules will need to disable this if they do not perform a build step, or have alternative build tooling (cli).
• While Metro is signalling that they would prefer that packages were not precompiled, the ecosystem is clearing moving towards things being precompiled. For example, react-native-builder-bob / react-native-reanimated / react-native-navigation all ship precompiled. https://bsky.app/profile/satya164.page/post/3ldf4egm2jk2q

All-in-all, when a module switches to this tsconfig we will need to

• Check for module specific overrides
• Fix the new strict mode errors
• Commit or disable the build dir being

This tsconfig does not yet include the changes to module. I suspect the changes to strict are enough work for now. The react-native repro just switched to esnext this week.

[github-actions]

Subscribed to pull request

File Patterns	Mentions
packages/expo-module-scripts/**	@ide

Generated by CodeMention

[expo-bot]

Hi there! 👋 I'm a bot whose goal is to ensure your contributions meet our guidelines.

I've found some issues in your pull request that should be addressed (click on them for more details) 👇

⚠️ Suggestion: Missing changelog entries

Your changes should be noted in the changelog, e.g.:
- Create tsconfig.next.json ([#33721](https://github.com/expo/expo/pull/33721) by [@marklawlor](https://github.com/marklawlor))
Read Updating Changelogs guide and consider adding an appropriate entry to the following changelogs:

• packages/expo-module-scripts/CHANGELOG.md

---

Generated by ExpoBot 🤖 against c6d3d79

[reichhartd]

Just to confirm, is it intended to use the community-based @tsconfig/react-native instead of the @react-native/typescript-config from the React Native monorepo?

[marklawlor]

We should use the official one, this was a mistake

[reichhartd]

While Metro is signalling that they would prefer that packages were not precompiled, the ecosystem is clearing moving towards things being precompiled. For example, react-native-builder-bob / react-native-reanimated / react-native-navigation all ship precompiled. https://bsky.app/profile/satya164.page/post/3ldf4egm2jk2q

What are the reasons that these libraries choose to ship their code precompiled, even though Metro prefers non-precompiled packages? In contrast, there is a trend in the Expo repository this year towards shipping TypeScript source files, as seen in the following pull requests: #33781, #30665, #29702, #29244.

[marklawlor]

@reichhartd We should ship both src and build. While Metro prefers using src, other tools do not. Jest is a common example as it requires additional setup to work with React Native. We also see community members trying to use Expo packages with other bundlers such as Next.js

Metro supports conditional exports with a react-native condition, so we should be able to satisfy both use cases

 "exports": {
    "browser": "./dist/index.js",
    "react-native": "./src/index.js",
    "default": "./dist/index.js"
  }