docsify/tsconfig.json
Joe Pea b960519608
feat: output type definitions, and allow new Docsify(opts) to accept options for ESM usage (#2392)
This `new Docsify(opts)` API can be safely converted to a Custom Element constructor with backwards compatibility later.
2025-12-03 21:49:44 -08:00

35 lines
1.3 KiB
JSON

{
"compilerOptions": {
"allowJs": true,
"checkJs": true,
"module": "esnext",
"moduleResolution": "node",
"target": "es2023",
"lib": ["ES2023", "DOM", "DOM.AsyncIterable", "DOM.Iterable"],
"declaration": true,
"declarationMap": true, // This (along with also shipping src/, not only dist/), makes "Go To Definition" go to the source files in IDEs for a better DX.
"emitDeclarationOnly": true,
"resolveJsonModule": true,
// Output declarations next to source files (the default when outDir is not
// defined), rather than in dist/, to avoid conflicting with the global
// build in dist/.
// "outDir": "dist/",
"strict": true,
"skipLibCheck": true,
"skipDefaultLibCheck": true,
// TODO: Remove once tinydate import is refactored to non-default, or replace/delete non-standards-aligned libs.
// Enables default import interop for CJS modules like tinydate
"allowSyntheticDefaultImports": true,
// TODO: Remove this once all implicit any errors are fixed with proper JSDoc types
// Currently suppressing ~600 implicit any errors across the codebase
// See: https://github.com/docsifyjs/docsify/pull/2392
"noImplicitAny": false
},
"include": ["src/**/*.js", "src/core/modules.ts", "src/core/globals.ts"]
}