Yoshihiro OKUMURA
bed2435ba2
The config files had drifted from what `npm create vite` scaffolds, and the build printed two warnings on every run. - drop tsconfig options that are redundant or no longer used (resolveJsonModule, esModuleInterop, useDefineForClassFields, ...) and move both projects to ES2023 - keep erasableSyntaxOnly off for src: SortConditionOrderDir is an enum - keep strict on, which the current template omits - externalise fs so lokijs stops warning about it - split node_modules into a vendor chunk, which puts every chunk back under the 500 kB warning threshold without raising the limit - emit nested files under public/, which the previous flat walk dropped without reporting them
30 lines
903 B
JSON
30 lines
903 B
JSON
{
|
|
"compilerOptions": {
|
|
"tsBuildInfoFile": "./node_modules/.tmp/tsconfig.app.tsbuildinfo",
|
|
"target": "ES2023",
|
|
"lib": ["ES2023", "DOM", "DOM.Iterable"],
|
|
"module": "ESNext",
|
|
"types": ["vite/client"],
|
|
"allowArbitraryExtensions": true,
|
|
"skipLibCheck": true,
|
|
|
|
/* Bundler mode */
|
|
"moduleResolution": "bundler",
|
|
"allowImportingTsExtensions": true,
|
|
"verbatimModuleSyntax": true,
|
|
"moduleDetection": "force",
|
|
"noEmit": true,
|
|
"jsx": "react-jsx",
|
|
|
|
/* Linting */
|
|
"strict": true,
|
|
"noUnusedLocals": true,
|
|
"noUnusedParameters": true,
|
|
/* SortConditionOrderDir is an enum, which erasable syntax forbids. */
|
|
"erasableSyntaxOnly": false,
|
|
"noFallthroughCasesInSwitch": true,
|
|
"noUncheckedSideEffectImports": true
|
|
},
|
|
"include": ["src"]
|
|
}
|