Pin the typecheck to our uniform tiptap set

`tsc --noEmit` (first step of `npm run build`) type-checks the shared
@k6n/cms-editor sources, which resolve tiptap from the backoffice tree:
core 3.30.2 mixed with a nested markdown 3.32.2 whose Extension type no
longer fits the older core's `Extensions`. Our own node_modules holds a
uniform 3.32.2 set, so map @tiptap/* there in tsconfig paths. Vite does
not read tsconfig paths (it aliases @k6n/cms-editor manually), so
bundling and runtime resolution are untouched.

🤖 Generated with Codebuff
Co-Authored-By: Codebuff <noreply@codebuff.com>
This commit is contained in:
mats committed 2026-11-07 13:49:16 +01:00
1 parent b7849c0359
commit 5c5c34d25a
1 file changed
+13
+13
View File
@@ -14,6 +14,19 @@
"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",