go-bananas/web/tsconfig.app.json
Daniel Noulet 2967f1a5af
Some checks are pending
Build, test, publish, deploy / build-test (push) Waiting to run
Build, test, publish, deploy / publish (push) Blocked by required conditions
Build, test, publish, deploy / deploy-prd (push) Blocked by required conditions
refactor
2026-10-10 02:30:01 +02:00

37 lines
1.3 KiB
JSON

{
"compilerOptions": {
"target": "ES2023",
"lib": ["ES2023", "DOM", "DOM.Iterable"],
"module": "ESNext",
"moduleResolution": "bundler",
"jsx": "react-jsx",
"useDefineForClassFields": true,
"strict": true,
"noUncheckedIndexedAccess": true,
"noImplicitOverride": true,
"noFallthroughCasesInSwitch": true,
"noUnusedLocals": true,
"noUnusedParameters": true,
"exactOptionalPropertyTypes": false,
"allowImportingTsExtensions": false,
"verbatimModuleSyntax": true,
"isolatedModules": true,
"moduleDetection": "force",
"resolveJsonModule": true,
"noEmit": true,
"skipLibCheck": true,
"forceConsistentCasingInFileNames": true,
"types": ["vitest/globals", "@testing-library/jest-dom"],
"paths": { "@/*": ["./src/*"] }
},
// The production build must not compile test files. One test imports the shipped
// SDK source across packages (`sdk/src/*.js`) to drive the real custom elements; that
// coupling belongs to the test project (tsconfig.test.json), not to the app image
// build, where the SDK may not even be on disk yet. `tsc -p tsconfig.app.json` is what
// the Dockerfile runs, so tests are simply out of this project's file set.
"include": ["src"],
"exclude": ["src/**/*.test.ts", "src/**/*.test.tsx", "src/test"]
}