adminandClaude Sonnet 5
d3bf94799e
Next.js's production build type-checks the whole repo by tsconfig.json's default include glob, which picked up mobile/'s .tsx files once the Docker image's git checkout finally included mobile/ (first pull to include it) — none of mobile's own dependencies (react-native, expo-router, ...) are installed in that container, so the build failed outright. mobile/ is now excluded from tsconfig.json and .dockerignore; it's a separate app with its own tsconfig/package.json and was never meant to be type-checked or shipped as part of the web image. Also completes the mobile EAS/FCM push setup (app.json's extra.eas.projectId and googleServicesFile, google-services.json gitignored) and adds a 15s timeout around getExpoPushTokenAsync so a device that can't reach FCM fails visibly instead of hanging silently forever. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
35 lines
680 B
JSON
35 lines
680 B
JSON
{
|
|
"compilerOptions": {
|
|
"target": "ES2017",
|
|
"lib": ["dom", "dom.iterable", "esnext"],
|
|
"allowJs": true,
|
|
"skipLibCheck": true,
|
|
"strict": true,
|
|
"noEmit": true,
|
|
"esModuleInterop": true,
|
|
"module": "esnext",
|
|
"moduleResolution": "bundler",
|
|
"resolveJsonModule": true,
|
|
"isolatedModules": true,
|
|
"jsx": "react-jsx",
|
|
"incremental": true,
|
|
"plugins": [
|
|
{
|
|
"name": "next"
|
|
}
|
|
],
|
|
"paths": {
|
|
"@/*": ["./src/*"]
|
|
}
|
|
},
|
|
"include": [
|
|
"next-env.d.ts",
|
|
"**/*.ts",
|
|
"**/*.tsx",
|
|
".next/types/**/*.ts",
|
|
".next/dev/types/**/*.ts",
|
|
"**/*.mts"
|
|
],
|
|
"exclude": ["node_modules", "mobile"]
|
|
}
|