Strange issue when upgrading Deno about dax

[drewbitt]

Does this also happen if you write this same script in e.g. bash?

[Hexagon]

No, the problem seems to be related to Deno.execPath()

This works (using Deno.Command behind the scenes, and ["deno", "--version"] as command):

import { Cron } from "jsr:@hexagon/croner";
import { spawn } from "jsr:@cross/utils";

// Check deno version every fifth second
new Cron("*/10 * * * * *", async () => {
    try {
        const result = await spawn(["deno","--version"]);
        console.log("Success!");
        console.log(result);
    } catch (e) {
        console.error("Failure!");
        console.log(e);
    }
});

... but this gives the said error (using [Deno.execPath(), "--version"] as command);

import { Cron } from "jsr:@hexagon/croner";
import { spawn } from "jsr:@cross/utils";

// Check deno version every fifth second
new Cron("*/10 * * * * *", async () => {
    try {
        const result = await spawn([Deno.execPath(),"--version"]);
        console.log("Success!");
        console.log(result);
    } catch (e) {
        console.error("Failure!");
        console.log(e);
    }
});

Could it be that dax uses Deno.execPath() internally, and Deno.execPath() somehow get changed to /home/user/.deno/bin/deno (deleted) when deno is upgraded?

Edit: Yep, just removing (deleted) from Deno.execPath() resolves the problem in my example. This works [Deno.execPath().replace(" (deleted)",""),"--version"].