workaround for EACCESS / EPERM when bundled for single-file-executable

[xwxfox]

When i was playing around with the library myself i constantly ran into errors like below when running it in a compiled single-file-executable.

permission denied, mkdir '/$bunfs'
    path: "/$bunfs",
 syscall: "mkdir",
   errno: -13,
    code: "EACCES"
)

It seems to be bacause of the way bun's virtual fs paths are returned - and it could def be fixed in a cleaner way, but this does work as a temporary workaround.

All it does is detect $bunfs in the function that returns the currentModulePath - and instead makes it fallback to path.resolve(process.cwd(), "vfs")

I've tested it myself, and it works in single-file-executables.

sysinfo in case it matters later, tested on:
Bun v1.3.6-canary.22+3898ed5e3
Arch Linux x64 (Linux 6.17.7-zen)

[AlbertShown]

Thank you Jay 👍

Similar issue here #9, but we are looking for a way to embed dynamic libraries (.dll, .dynlib, .so) into single-file-executable.

[xwxfox]

Thank you Jay 👍

Similar issue here #9, but we are looking for a way to embed dynamic libraries (.dll, .dynlib, .so) into single-file-executable.

I've actually been working on something for this myself, once I get it more stable I'd love to share some more info :3

[Dialga]

Doesn't work:

$ bun build --compile .
   [5ms]  bundle  6 modules
  [40ms] compile  index
$ ./index
55 |     if (directory.startsWith("/")) {
56 |       directory = directory.slice(1);
57 |     }
58 |     directory = directory.replaceAll("/", "\\");
59 |   }
60 |     directory = resolve(homedir(), ".bun-webui");
                            ^
ReferenceError: resolve is not defined
      at <anonymous> (/$bunfs/root/.:60:24)
      at /$bunfs/root/.:75:3

Bun v1.3.5 (Linux x64)

[AlbertShown]

Error is : resolve is not defined.

I think we should just import it like this:

import { homedir } from "node:os";
import { resolve } from "node:path";