From e0187e772ed79256902029992894aa3dfee08160 Mon Sep 17 00:00:00 2001 From: Rick Staa Date: Tue, 18 Aug 2026 12:30:18 +0200 Subject: [PATCH] chore: commit the module resolution Next already enforces next 16.2 rewrites tsconfig.json on every dev and build run, setting moduleResolution to bundler, so the committed "node" value left every checkout permanently dirty and reserialized without Prettier. It also split resolution in two: CI type-checks a clean checkout with node, which ignores package.json exports maps, while Vercel builds with bundler, which honours them. That is how a private rainbowkit deep import passed typecheck for months. Co-Authored-By: Claude Opus 5 (1M context) --- tsconfig.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tsconfig.json b/tsconfig.json index c98be223..870a325a 100644 --- a/tsconfig.json +++ b/tsconfig.json @@ -17,7 +17,7 @@ "noEmit": true, "esModuleInterop": true, "module": "esnext", - "moduleResolution": "node", + "moduleResolution": "bundler", "resolveJsonModule": true, "isolatedModules": true, "jsx": "react-jsx",