mirror of
https://github.com/go-gitea/gitea
synced 2024-12-22 08:34:26 +00:00
d061f6b70a
Typescript 5.7 changed semantics around JSON imports and `nodenext` is now [treated differently](https://devblogs.microsoft.com/typescript/announcing-typescript-5-7-beta/#validated-json-imports-in---module-nodenext) than `node16` for JSON imports and it requires the import attribute, so change the value to that and add the attribute to eliminate this typescript error. [`moduleResolution`](https://www.typescriptlang.org/tsconfig/#moduleResolution) is treated as an alias when `module` is `nodenext`, so we don't need to specify it. Also see https://github.com/microsoft/TypeScript/issues/60589. It appears the next Typescript release will fix this for `node16`, but I guess it'll still be good to switch to `nodenext`.
35 lines
840 B
JSON
35 lines
840 B
JSON
{
|
|
"include": [
|
|
"*",
|
|
"tests/e2e/**/*",
|
|
"tools/**/*",
|
|
"web_src/js/**/*",
|
|
],
|
|
"compilerOptions": {
|
|
"target": "es2020",
|
|
"module": "nodenext",
|
|
"lib": ["dom", "dom.iterable", "dom.asynciterable", "esnext"],
|
|
"allowImportingTsExtensions": true,
|
|
"allowJs": true,
|
|
"allowSyntheticDefaultImports": true,
|
|
"alwaysStrict": true,
|
|
"esModuleInterop": true,
|
|
"isolatedModules": true,
|
|
"noEmit": true,
|
|
"resolveJsonModule": true,
|
|
"skipLibCheck": true,
|
|
"verbatimModuleSyntax": true,
|
|
"stripInternal": true,
|
|
"strict": false,
|
|
"noUnusedLocals": true,
|
|
"noUnusedParameters": true,
|
|
"noPropertyAccessFromIndexSignature": false,
|
|
"exactOptionalPropertyTypes": false,
|
|
"sourceMap": true,
|
|
"types": [
|
|
"vitest/globals",
|
|
"./web_src/js/globals.d.ts",
|
|
],
|
|
}
|
|
}
|