القائمة
Synchronizes tsconfig.json paths from package.json imports field. Ensures TypeScript resolves subpath imports (#imports) correctly during development.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | syncing-tsconfig-paths |
| description | Synchronizes tsconfig.json paths from package.json imports field. Ensures TypeScript resolves subpath imports (#imports) correctly during development. |
Tsconfig paths are automatically kept in sync with package.json subpath imports by the kitz/subpath-imports-integrity oxlint rule (Check 5: tsconfig drift).
The lint rule (packages/oxlint-rules/plugin.mjs) compares tsconfig.json paths against package.json imports for each package. When drift is detected, it:
subpathImportsIntegrityTsconfigDrift diagnosticRun the linter to trigger the autofix:
pnpm check:lint
Check for drift without fixing:
pnpm check:lint 2>&1 | grep "subpath-imports-integrity"
The rule transforms package.json imports to tsconfig paths:
"#pkg": "./src/_.ts" → "#pkg": ["./src/_.js"]
Key behavior:
#kitz/* entries are preserved (manually maintained for circular devDep workaround).ts to .js (TypeScript with nodenext resolves .js → .ts)Add a namespace/module to a @kitz package — including extending the @kitz/effect namespaces. Covers the _.ts/__.ts barrel pattern, the package exports map, and import conventions.
Audits the project for consistency issues that may arise from manual editing. Checks package scripts, tsconfig paths, README tables, and other conventions.
Authors and manages global package scripts using the _: prefix convention. Scripts defined in root package.json are propagated to all packages with the prefix stripped.
Creates commits following project conventions. Handles Conventional Commits with project-specific scopes, PR title requirements, and CI validation rules.
Create a new @kitz/<concept> package via the Vite+ generator. Scaffolds package.json (live-types exports + effect peer), the layered tsconfigs, and the namespace barrel, then wires it into the workspace.
Use when adding project conventions, coding rules, or guidelines. Determines correct location and scoping based on which packages the rule applies to.