fix: correct gptscript bin path behavior

There is a big difference between running the tests and importing this
as a module, specifically when not setting GPTSCRIPT_BIN. This change
addresses these differences to allow both contexts to work.

Author: thedadams

package.json

@@ -53,6 +53,7 @@
     "url": "^0.11.3"
   },
   "jest": {
+    "preset": "ts-jest/presets/default-esm",
     "transform": {
       "^.+\\.ts?$": [
         "ts-jest",

scripts/install-binary.js

@@ -85,7 +85,7 @@ const suffix = {
 
 const url = `${gptscript_info.url}${gptscript_info.version}/gptscript-${gptscript_info.version}-${pltfm}-${arch}.${suffix}`;
 
-const outputDir = path.resolve('..', 'bin');
+const outputDir = path.resolve('bin');
 
 const fileExist = (path) => {
     try {

src/gptscript.ts

@@ -668,7 +668,7 @@ function getCmdPath(): string {
 		return process.env.GPTSCRIPT_BIN
 	}
 
-	return path.join(path.dirname(fileURLToPath(import.meta.url)), "..", "..", "bin", "gptscript")
+	return path.join(path.dirname(fileURLToPath(import.meta.url)), "..", "bin", "gptscript")
 }
 
 function parseBlocksFromNodes(nodes: any[]): Block[] {

tests/gptscript.test.ts

@@ -1,7 +1,9 @@
 import * as gptscript from "../src/gptscript"
 import path from "path"
+import {fileURLToPath} from "url"
 
 let client: gptscript.Client
+const __dirname = path.dirname(fileURLToPath(import.meta.url))
 
 describe("gptscript module", () => {
 	beforeAll(async () => {

tsconfig.json

@@ -2,7 +2,7 @@
   "compilerOptions": {
     "target": "esnext",
     "module": "esnext",
-    "moduleResolution": "bundler",
+    "moduleResolution": "node",
     "rootDir": "./src",
     "declaration": true,
     "outDir": "./dist",