@kyh/tsconfig 1.1.13 → 1.2.0

package/README.md

@@ -0,0 +1,31 @@
+# @kyh/tsconfig
+
+Shared TypeScript configs.
+
+## Install
+
+```bash
+pnpm add -D @kyh/tsconfig
+```
+
+## Usage
+
+```jsonc
+// tsconfig.json
+{
+  "extends": "@kyh/tsconfig/base.json",
+  "include": ["src"]
+}
+```
+
+Configs:
+
+- `base.json` — strict, `noUncheckedIndexedAccess`, bundler resolution, `noEmit`
+
+`base.json` is the only config, and it's for **workspace packages and apps**. Point their
+`exports` straight at source (`"." : "./src/index.ts"`) and give them no build step: tsserver
+and the bundler both follow `exports` and read the `.ts`, so emitting `.d.ts` for them produces
+artifacts nothing resolves.
+
+Packages **published to npm** should not extend this at all — they inline their own tsconfig so
+they build without depending on a shared workspace config.

package/base.json

@@ -3,8 +3,8 @@
   "compilerOptions": {
     "esModuleInterop": true,
     "skipLibCheck": true,
-    "target": "ES2022",
-    "lib": ["ES2022"],
+    "target": "ES2023",
+    "lib": ["ES2023"],
     "allowJs": true,
     "resolveJsonModule": true,
     "moduleDetection": "force",

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "@kyh/tsconfig",
-  "version": "1.1.13",
-  "publishConfig": {
-    "access": "public"
-  },
+  "version": "1.2.0",
   "files": [
     "*.json"
-  ]
+  ],
+  "publishConfig": {
+    "access": "public"
+  }
 }

package/internal-package.json

@@ -1,11 +0,0 @@
-{
-  "$schema": "https://json.schemastore.org/tsconfig",
-  "extends": "./base.json",
-  "compilerOptions": {
-    "declaration": true,
-    "declarationMap": true,
-    "emitDeclarationOnly": true,
-    "noEmit": false,
-    "outDir": "${configDir}/dist"
-  }
-}