Sanniv Khare 6 min read

TypeScript 7.1 beta on React Native 0.88.1: tested with tsc

TypeScript 7.1 beta on React Native 0.88.1: tested with tsc

Short version: a fresh React Native 0.88.1 app type-checks with TypeScript 7.1.0-beta with zero errors, exactly as it does with 7.0.2 and with the 6.0.3 the template still installs. The one change you will notice is in the lib: 7.1 adds es2026 as a --target and --lib value, and Promise.allKeyed now type-checks under React Native’s own @react-native/typescript-config, because that config already pulls in esnext.promise. Type-checking a method does not mean Hermes ships it, so treat that as the thing to check.

We ran this on 16 Nov 2026 on a Linux test server (Ubuntu 24.04, 2 vCPU, Node 22.23.4) with the @react-native-community/template 0.88.1 project, its stock tsconfig.json, and three compilers: typescript 6.0.3, 7.0.2 (npm latest) and 7.1.0-beta (npm beta, published 20 Oct 2026). On that date the npm rc tag still points to 7.0.1-rc, so there is no 7.1 RC yet.

Why we did this: our React Native banking and TV apps run a tsc --noEmit step in CI on every pull request, and we want to know before the 7.1 RC whether bumping the compiler costs us anything. This follows our earlier TypeScript 7 on React Native 0.88 timing post and the strict TypeScript API deep-import tests.

What the 0.88.1 template ships

The 0.88.1 community template pins "typescript": "^6.0.3" in devDependencies and extends @react-native/typescript-config 0.88.1. That config sets target and module to esnext, moduleResolution to bundler, customConditions to ["react-native"], strict, noEmit, skipLibCheck, and a hand-picked lib list that stops at es2024.promise plus esnext.promise. That lib list matters below.

So a new React Native project is on TypeScript 6 until you change it. Moving to 7 is a one-line devDependencies change; nothing in the shipped config is rejected by 7.0.2 or 7.1.0-beta.

npm install --save-dev typescript@beta
npx tsc -v          # Version 7.1.0-beta
npx tsc --noEmit -p .

Errors and timings on the stock project

tsc --noEmit run three times with TypeScript 6.0.3, 7.0.2 and 7.1.0-beta on a fresh React Native 0.88.1 app

Real output from our test server, trimmed to one line per compiler.

All three compilers report zero errors on the untouched template. --extendedDiagnostics counts 317 files for 6.0.3 and 7.0.2 and 318 for 7.1.0-beta; with skipLibCheck on, the check itself takes about 0.01 s on 7.x, so the wall-clock numbers above are mostly process start-up. On a project this small the gap between 7.0.2 and 7.1 beta is noise; the gap to 6.0.3 is the native compiler.

For larger codebases, Microsoft’s beta announcement reports its own 7.0 vs 7.1 Beta benchmarks under --noEmit with four checker threads, for example mui-docs going from 22.2 s to 11.9 s. Those are Microsoft’s numbers on its machines, not ours.

What 7.1 changes, and what showed up in the RN project

We built this table from the TypeScript 7.1 Beta announcement (20 Oct 2026) and checked each row against the template project with small probe files.

Change in 7.1 beta Seen in the RN 0.88.1 project Source
es2026 is a stable --target and --lib value (Math.sumPrecise, Error.isError, Map.getOrInsert, Array.fromAsync and more) Yes: 7.0.2 rejects "lib": ["es2026"] with TS6046; 7.1 accepts it beta post
New esnext methods: Promise.allKeyed, Promise.allSettledKeyed, Iterator.zip, Iterator.prototype.chunks and others Yes: Promise.allKeyed type-checks under the stock RN config beta post
Import attributes in ambient modules (declare module "*" with { type: "css" }) No: nothing in the template uses import attributes beta post
Source phase imports (import source x from "...") No: needs esnext in lib or target, and Metro has no use for it today beta post
New API entry points (typescript/sync, typescript/async, typescript/ast) and content mappers behind --runExternalCode No: affects tools built on the compiler API, not tsc --noEmit beta post
Stricter checks on distributive conditional types with constraints No: zero errors on the template and on our two probe generics beta post
DOM lib.d.ts regenerated No: the RN config does not include dom beta post

The lib change, up close

We added two probe files to the template: one calling Math.sumPrecise, Error.isError and Map.getOrInsert, one calling Promise.allKeyed. Same files, same tsconfig.json, two compilers:

The same probe files type-checked with TypeScript 7.0.2 and 7.1.0-beta: the lib hint changes to es2026 and Promise.allKeyed stops erroring

Error output from both compilers, shortened to fit.

Two things changed:

  1. The hint now says es2026. 7.0.2 suggests changing lib to esnext; 7.1.0-beta suggests es2026. The errors themselves remain, because RN’s config does not list es2026.
  2. Promise.allKeyed is accepted. In 7.1.0-beta its declaration lives in lib.esnext.promise.d.ts, and @react-native/typescript-config includes esnext.promise. So code written against 7.1 can call Promise.allKeyed without a type error, while the same code fails tsc on 7.0.2.

That second point is the one to watch in a team. If one developer runs 7.1 and CI runs 7.0, a pull request can pass locally and fail in CI. More importantly, a passing type check says nothing about the JavaScript engine: whether Hermes in your React Native version implements Promise.allKeyed is a separate question, and the type check will not answer it. Until you have checked your engine, keep these calls behind a polyfill or out of shipped code.

If you do want the es2026 declarations, this is the smallest change that type-checks cleanly with 7.1.0-beta (and fails with TS6046 on 7.0.2):

{
  "extends": "./tsconfig.json",
  "compilerOptions": {
    "lib": ["es2026", "esnext.promise"]
  }
}

With this file, 7.1.0-beta reports zero errors on the template plus all probe files.

What to do before the 7.1 RC

  • Pin the compiler in one place. Put the exact version in devDependencies ("typescript": "7.1.0-beta" or "7.0.2"), not a caret range that crosses the 6 to 7 line, so local runs and CI agree.
  • Grep for the new lib methods. allKeyed, allSettledKeyed, sumPrecise, getOrInsert, Iterator.zip: if they appear, decide on a polyfill before 7.1 makes them type-check silently.
  • Leave the RN lib list alone unless you need it. The stock list worked unchanged on all three compilers. Adding es2026 only buys declarations, not runtime support.
  • Watch tooling, not tsc. The new API entry points matter to ESLint plugins, codegen and editors built on the compiler API. Those are where a 7.x bump is more likely to bite than in tsc --noEmit.
  • Run your own check on the RC. The steps above take a minute on a real project: install, tsc -v, tsc --noEmit -p ., and diff the error list against your current compiler.

How we tested

  • Project: npm pack @react-native-community/template@0.88.1, dependencies installed with npm install --ignore-scripts; no native build is involved in a type check.
  • Compilers: typescript 6.0.3 (template), 7.0.2 and 7.1.0-beta, each run three times with tsc --noEmit -p . and once with --extendedDiagnostics.
  • Probe files: three small .ts files, two for the lib methods and one with two constrained distributive generics, removed again afterwards.
  • Machine: Linux test server, Ubuntu 24.04, 2 vCPU, Node 22.23.4, 16 Nov 2026.

Made by the team behind this post

Apps from our studio

  • Nix

    The Mac uninstaller that finds what the Trash leaves behind: caches, logs, derived data and saved states.

    macOS

    Get
  • Cardigami

    Pop-up greeting cards that rise out of the fold on iPhone Duo.

    iPhone · App Store

    Get
  • BMDB.fun

    Your Bollywood world at a glance, with links straight to the OTT app that streams each film.

    Android TV · Web · Mobile

    Get
  • OneClick QuitAll

    Quit every running app in one click. See memory and CPU first.

    macOS · Mac App Store

    Get

Need this built? Let’s talk.

We build and run apps for Mac, TV, mobile and the web, and write about what we learn.