fix(tsconfig): unblock shared-types consumers

shared-types/src/index.ts re-exports with explicit .ts extensions
(Tailwind v4 module resolver needs them). TS 5.7 requires consumers
to opt in via allowImportingTsExtensions. The flag only type-checks
when noEmit:true; the NestJS builder also needs
rewriteRelativeImportExtensions so tsc still emits valid JS.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

apps/todo/packages/shared/tsconfig.json

@@ -3,6 +3,10 @@
 		"target": "ES2022",
 		"module": "ESNext",
 		"moduleResolution": "bundler",
+		// shared-types re-exports with explicit .ts paths (Tailwind v4
+		// module resolver needs them). Consumers need this opt-in;
+		// noEmit:true means no rewrite flag is required.
+		"allowImportingTsExtensions": true,
 		"strict": true,
 		"esModuleInterop": true,
 		"skipLibCheck": true,

games/arcade/apps/web/tsconfig.json

@@ -9,6 +9,7 @@
 		"skipLibCheck": true,
 		"sourceMap": true,
 		"strict": true,
-		"moduleResolution": "bundler"
+		"moduleResolution": "bundler",
+		"allowImportingTsExtensions": true
 	}
 }

packages/shared-types/tsconfig.json

@@ -3,6 +3,12 @@
 		"target": "ES2022",
 		"module": "ESNext",
 		"moduleResolution": "bundler",
+		// src/index.ts re-exports with explicit .ts extensions (needed so
+		// Tailwind's module resolver can follow the package out of its
+		// bundler when scanning branded components). noEmit:true means
+		// the rewrite flag isn't needed — this is the matching compiler
+		// opt-in that lets tsc see the .ts imports without erroring.
+		"allowImportingTsExtensions": true,
 		"lib": ["ES2022"],
 		"strict": true,
 		"esModuleInterop": true,

services/mana-landing-builder/tsconfig.json

@@ -6,6 +6,8 @@
 		"emitDecoratorMetadata": true,
 		"experimentalDecorators": true,
 		"allowSyntheticDefaultImports": true,
+		"allowImportingTsExtensions": true,
+		"rewriteRelativeImportExtensions": true,
 		"target": "ES2022",
 		"sourceMap": true,
 		"outDir": "./dist",