Fix resolving external packages that are ESM only (#1346)

* Fix resolving external packages that are ESM only by falling back to mlly resolvePathSync. This will fix mupdf

* when publishing a prerelease and aborting, clear the git stage

Author: ericallam

.changeset/heavy-jobs-push.md

@@ -0,0 +1,5 @@
+---
+"trigger.dev": patch
+---
+
+Fix resolving external packages that are ESM only by falling back to mlly resolvePathSync. This will fix mupdf

packages/cli-v3/e2e/fixtures.ts

@@ -179,4 +179,38 @@ export const fixturesConfig: TestCase[] = [
       },
     ],
   },
+  {
+    id: "esm-only-external",
+    buildManifestMatcher: {
+      runtime: "node",
+      externals: [
+        {
+          name: "import-in-the-middle",
+          version: "1.11.0",
+        },
+        {
+          name: "mupdf",
+          version: "0.3.0",
+        },
+      ],
+      files: [{ entry: "src/trigger/helloWorld.ts" }],
+    },
+    workerManifestMatcher: {
+      tasks: [
+        {
+          id: "helloWorld",
+          filePath: "src/trigger/helloWorld.ts",
+          exportName: "helloWorld",
+        },
+      ],
+    },
+    runs: [
+      {
+        task: { id: "helloWorld", filePath: "src/trigger/helloWorld.ts", exportName: "helloWorld" },
+        payload: "{}",
+        result: { ok: true, durationMs: 1 },
+      },
+    ],
+    tsconfig: "tsconfig.json",
+  },
 ];

packages/cli-v3/e2e/fixtures/esm-only-external/.yarnrc.yml

@@ -0,0 +1 @@
+nodeLinker: node-modules