{
  "compilerOptions": {
    "target": "ES2022",
    "lib": ["ES2023", "DOM", "DOM.Iterable"],
    "module": "ESNext",
    "moduleResolution": "bundler",
    "jsx": "react-jsx",
    "strict": true,
    "noUncheckedIndexedAccess": false,
    "skipLibCheck": true,
    "isolatedModules": true,
    "allowImportingTsExtensions": true,
    "noEmit": true,
    "types": ["vite/client", "node"],
    "baseUrl": ".",
    "paths": {
      // Our own node_modules holds a uniform @tiptap/* set (3.32.2). The shared
      // @k6n/cms-editor sources below resolve tiptap from the backoffice tree,
      // which mixes core 3.30.2 with a nested markdown 3.32.2 whose Extension
      // type is no longer assignable to the older core's `Extensions` - that
      // version drift broke `tsc --noEmit` (first step of `npm run build`).
      // Pin the check to our uniform set. Vite does not read tsconfig paths
      // (it aliases @k6n/cms-editor manually), so bundling is untouched.
      "@tiptap/core": ["./node_modules/@tiptap/core"],
      "@tiptap/pm": ["./node_modules/@tiptap/pm"],
      "@tiptap/pm/*": ["./node_modules/@tiptap/pm/*"],
      "@tiptap/starter-kit": ["./node_modules/@tiptap/starter-kit"],
      "@tiptap/extension-image": ["./node_modules/@tiptap/extension-image"],
      "@tiptap/markdown": ["./node_modules/@tiptap/markdown"],
      "@k6n/cms-editor": [
        "../backoffice/web/packages/cms-editor/src/index.ts",
        "../ecommerce/backoffice/web/packages/cms-editor/src/index.ts",
        "./.cms-editor/src/index.ts"
      ]
    }
  },
  "include": ["src", "mock", "vite", "vite.config.ts", "test"]
}