fix: properly handle import.meta.url with ESM support

Use import.meta.url to resolve SDK paths from file location instead of
process.cwd(). This ensures templates are found correctly whether kitdot
is run from source or installed as a global package.

Changes:
- Use import.meta.url with fileURLToPath to get current file directory
- Search upward from file location to find package.json with name='kitdot'
- Fallback to cwd search if file-based search fails (for test compat)
- Enable Node's experimental VM modules for Jest ESM support
- Inline TypeScript config in jest.config.cjs (remove tsconfig.test.json)
- Configure ts-jest with ES2022 module support

All 73 tests passing locally.

Author: nomadbitcoin

jest.config.cjs

@@ -13,7 +13,13 @@ module.exports = {
   transform: {
     '^.+\\.(ts|js)$': ['ts-jest', {
       useESM: true,
-      tsconfig: 'tsconfig.test.json'
+      tsconfig: {
+        module: 'ES2022',
+        target: 'ES2022',
+        moduleResolution: 'node',
+        esModuleInterop: true,
+        resolveJsonModule: true
+      }
     }]
   },
   moduleNameMapper: {

package.json

@@ -13,8 +13,8 @@
     "start": "node dist/cli.js",
     "lint": "eslint src/**/*.ts",
     "lint:fix": "eslint src/**/*.ts --fix",
-    "test": "jest",
-    "test:templates": "jest --testPathPattern=template-validation",
+    "test": "node --experimental-vm-modules node_modules/jest/bin/jest.js",
+    "test:templates": "node --experimental-vm-modules node_modules/jest/bin/jest.js --testPathPattern=template-validation",
     "prepublishOnly": "npm run build"
   },
   "keywords": [

src/utils/sdk-paths.ts

@@ -1,11 +1,19 @@
 // src/sdk-paths.ts
 import fs from "fs";
 import path from "path";
+import { fileURLToPath } from "url";
 
-// Find the SDK root by searching upward from current working directory
-// This approach works in all environments without needing import.meta or __dirname
+// Get the directory of this source file
+// In production: dist/utils/sdk-paths.js
+// In development: src/utils/sdk-paths.ts
+function getFileDir(): string {
+  return path.dirname(fileURLToPath(import.meta.url));
+}
+
+// Find the SDK root by searching upward from this file's location
+// This works whether the package is installed globally or run from source
 function findSDKRootSync(): string {
-  let dir = process.cwd();
+  let dir = getFileDir();
   const maxUp = 10; // Search up to 10 levels
 
   for (let i = 0; i < maxUp; i++) {
@@ -14,7 +22,7 @@ function findSDKRootSync(): string {
       try {
         const pkg = JSON.parse(fs.readFileSync(packageJsonPath, 'utf-8'));
         // Check if this is the kitdot package
-        if (pkg.name === 'kitdot' || fs.existsSync(path.join(dir, 'templates'))) {
+        if (pkg.name === 'kitdot') {
           return dir;
         }
       } catch (_e) {
@@ -26,8 +34,26 @@ function findSDKRootSync(): string {
     dir = parent;
   }
 
-  // Fallback to cwd if we can't find the SDK root
-  return process.cwd();
+  // Fallback: search from cwd (useful for tests)
+  dir = process.cwd();
+  for (let i = 0; i < maxUp; i++) {
+    const packageJsonPath = path.join(dir, "package.json");
+    if (fs.existsSync(packageJsonPath)) {
+      try {
+        const pkg = JSON.parse(fs.readFileSync(packageJsonPath, 'utf-8'));
+        if (pkg.name === 'kitdot') {
+          return dir;
+        }
+      } catch (_e) {
+        // Invalid package.json, continue searching
+      }
+    }
+    const parent = path.dirname(dir);
+    if (parent === dir) break;
+    dir = parent;
+  }
+
+  throw new Error('Could not find kitdot package root');
 }
 
 // Cache the SDK root