feat: add TypeScript 7 support

.github/workflows/ci.yml

@@ -0,0 +1,32 @@
+name: ci
+on:
+  pull_request:
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  validate-configs:
+    name: validate configs (typescript ${{ matrix.typescript }})
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        typescript: [ 6, 7 ]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Use Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version-file: '.nvmrc'
+          cache: 'npm'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Install typescript ${{ matrix.typescript }}
+        run: npm install --no-save typescript@${{ matrix.typescript }}
+
+      - name: Validate configs
+        run: npm run validate-configs

.gitignore

@@ -114,3 +114,6 @@ Temporary Items
 
 .idea/
 public/
+
+# scripts/validate-configs.mjs scratch dir (created and removed at runtime)
+.tmp-validate-*/

README.md

@@ -8,7 +8,8 @@ This package contains a universal tsconfig file that is optimized for browser, l
 
 ## Compatibility
 
-- `@getresponse/tsconfig@2.x` - TypeScript >=6.0.0 <7.0.0
+- `@getresponse/tsconfig@3.x` - TypeScript >=6.0.0 <8.0.0
+- `@getresponse/tsconfig@2.x` - TypeScript >=6.0.0 <7.0.0 (no longer maintained)
 - `@getresponse/tsconfig@1.x` - TypeScript 5.x (no longer maintained)
 
 ## Installation
@@ -74,4 +75,11 @@ This package contains a universal tsconfig file that is optimized for browser, l
 
    Note: `node-lts` configs already include `"types": ["node"]` by default.
 
+6. `tsconfig.base.json`, `lib/tsconfig.esm.json`, and `node-lts/tsconfig.json` use `"moduleResolution": "nodenext"`, which requires:
+
+   - `"type": "module"` in your project's `package.json`
+   - explicit file extensions on relative imports, e.g. `import { helper } from './helper.js'` (not `'./helper'`), even though the source file is `helper.ts`
+
+   `browser/tsconfig.json`, `lib/tsconfig.cjs.json`, and `node-lts/tsconfig.cjs.json` use `"moduleResolution": "bundler"` instead and are not affected by either requirement.
+
 That's it! Now you can enjoy the benefits of using a standardized tsconfig file in your TypeScript projects.

configs/browser/tsconfig.json

@@ -1,3 +1,7 @@
 {
   "extends": "../tsconfig.base.json",
+  "compilerOptions": {
+    "module": "esnext",
+    "moduleResolution": "bundler"
+  }
 }

configs/lib/tsconfig.cjs.json

@@ -2,5 +2,6 @@
   "extends": "./tsconfig.esm.json",
   "compilerOptions": {
     "module": "commonjs",
+    "moduleResolution": "bundler"
   }
 }

configs/node-lts/tsconfig.cjs.json

@@ -1,8 +1,8 @@
 {
   "extends": "./tsconfig.json",
   "compilerOptions": {
-    "emitDecoratorMetadata": true,
     "module": "commonjs",
+    "moduleResolution": "bundler",
     "target": "es2022"
   }
 }

configs/node-lts/tsconfig.json

@@ -2,7 +2,7 @@
   "extends": "../tsconfig.base.json",
   "compilerOptions": {
     "emitDecoratorMetadata": true,
-    "module": "es2022",
+    "experimentalDecorators": true,
     "target": "es2022",
     "types": ["node"]
   }

configs/tsconfig.base.json

@@ -6,7 +6,7 @@
     "sourceMap": true,
     "allowJs": false,
     "jsx": "react",
-    "module": "esnext",
+    "module": "nodenext",
     "moduleResolution": "nodenext",
     "noImplicitReturns": true,
     "noUnusedLocals": false,