k, well dev needs an unmodified env

Otherwise when unsetting the env the polluted additions remain. There’s probably more complicated ways to solve this, but assuming `pkgx` is in the PATH is reasonable for the usage of this tool IMO.
pkgxdev · Jan 7, 2025 · 2238454 · 2238454 · jhheider · Jan 7, 2025
1 parent 28cc0fd
commit 2238454
Showing 1 changed file with 5 additions and 3 deletions.
diff --git a/projects/pkgx.sh/dev/package.yml b/projects/pkgx.sh/dev/package.yml
@@ -7,8 +7,9 @@ display-name: dev
 versions:
   github: pkgxdev/dev
 
-dependencies:
-  pkgx.sh: ^1,^2
+# strictly needed but breaks `dev` as it needs a virgin env
+# dependencies:
+  # pkgx.sh: ^1,^2
 
 build:
   - mkdir -p {{prefix}}/bin {{prefix}}/share/pkgx/dev
@@ -19,7 +20,8 @@ build:
     prop: |
       #!/bin/sh
       d="$(cd "$(dirname $0)"/.. && pwd)"
-      exec "$d/share/pkgx/dev/app.ts" "$@"
+      deno="$(pkgx +deno -- which deno)"
+      exec "$deno" run -A "$d/share/pkgx/dev/app.ts" "$@"
 provides:
   - bin/dev