@dbx-tools/projen 0.6.39 → 0.6.40

package/package.json

@@ -9,9 +9,9 @@
   },
   "dependencies": {
     "@clack/prompts": "^1.7.0",
-    "@dbx-tools/core": "^0.6.39",
-    "@dbx-tools/path": "^0.6.39",
-    "@dbx-tools/shared-core": "^0.6.39",
+    "@dbx-tools/core": "^0.6.40",
+    "@dbx-tools/path": "^0.6.40",
+    "@dbx-tools/shared-core": "^0.6.40",
     "commander": "^15.0.0",
     "concurrently": "^10.0.3",
     "constructs": "^10.6.0",
@@ -32,7 +32,7 @@
   },
   "main": "index.ts",
   "license": "Apache-2.0",
-  "version": "0.6.39",
+  "version": "0.6.40",
   "types": "index.ts",
   "type": "module",
   "exports": {

package/src/project.ts

@@ -746,15 +746,16 @@ function registerRootTasks(project: javascript.NodeProject): void {
 }
 
 /**
- * `tsx <rel>/tasks/<script>` command for a projen task, relative to `project.outdir`.
- * Resolves the engine's `tasks/` dir off its installed package root (via
- * {@link resolvePkgRoot}), so it works both in-repo and when the engine is a
- * dependency in a consumer's `node_modules` - no filesystem walking.
+ * `tsx node_modules/@dbx-tools/projen/tasks/<script>` command for a projen task.
+ *
+ * Use the stable package symlink, never `require.resolve()`'s physical pnpm
+ * store path. A later install can change the peer-hash directory while leaving
+ * the package symlink valid; persisting the physical path made every generated
+ * task fail with ERR_MODULE_NOT_FOUND after such an update.
  */
-export function taskScript(project: javascript.NodeProject, script: string, args = ""): string {
-  const scriptPath = join(resolvePkgRoot(), "tasks", script);
-  const rel = toPosix(relative(resolve(project.outdir), scriptPath));
-  return args ? `tsx ${rel} ${args}` : `tsx ${rel}`;
+export function taskScript(_project: javascript.NodeProject, script: string, args = ""): string {
+  const scriptPath = toPosix(join("node_modules", "@dbx-tools", "projen", "tasks", script));
+  return args ? `tsx ${scriptPath} ${args}` : `tsx ${scriptPath}`;
 }
 
 /**