Next.js 16.3 and native TypeScript 7

Both current starter kits now ship Next.js 16.3.0 and TypeScript 7.0.2. This coordinated update moves the application compiler to the native TypeScript 7 toolchain while keeping the Prisma and Drizzle editions aligned.

What changed

• Updated next and @next/bundle-analyzer from 16.2.12 to 16.3.0.
• Updated the project compiler from TypeScript 6.0.3 to 7.0.2.
• Kept the existing React 19.2.8 runtime unchanged.
• Updated Pro Prisma's client, PostgreSQL adapter and CLI from 7.9.0 to 7.9.1 after the patch release resolved newly reported dependency advisories.
• Added explicit PostgreSQL types to Pro Drizzle.
• Updated the Drizzle MCP schema parser to use Microsoft's official @typescript/typescript6 compatibility package.

TypeScript 7 does not expose the stable JavaScript compiler API used by the Drizzle MCP parser. The compatibility package supplies that API only to the parser; application type checking still runs on TypeScript 7.

Deliberate scope

Next.js 16.3 also introduces opt-in features such as Instant Navigations. This release does not enable those features or change the kits' caching model. The framework and compiler upgrade is intentionally separate from behavioral application changes.

Existing projects

Update the framework, matching analyzer and compiler together, then regenerate the npm lockfile:

npm install --save-exact next@16.3.0 @next/bundle-analyzer@16.3.0
npm install --save-dev --save-exact typescript@7.0.2

Projects that import the TypeScript compiler API should read the official TypeScript 7 migration guidance before removing TypeScript 6 from their tooling.

No database migration is required. Both Achromatic editions were checked from clean lockfile installs with TypeScript 7 type checking, MCP compilation, Oxlint, Oxfmt, unit tests and production builds.

Read the upgrade guide for the compatibility checks that matter before adopting the new toolchain.