Is bun build --compile + Bun Worker + import {} from "" a bad approach?

[deanrih]

So I don't know if this is Bun's bug, limitation, or user error and skill issue (most likely), so I put this here instead.

I have a project with setup like this

- src
  - /db/ # drizzle config, schema, and wrappers
  - /service/ # core app
  - /helper/ # helper/utils, including worker-loader
    - worker-loader.ts
  - /worker/ # all worker files
    - worker-target.worker.ts
  - index.ts
  - ...
- package.json
- tsconfig.json
- ...

with tsconfig like this

{
  "compilerOptions": {
    ...
    "paths": {
      "~/*": [
        "src/*"
      ]
    }
  }
}

worker-loader.ts

// @ts-expect-error
import workerTarget from "~/worker/worker-target.worker" with { type: "file" }; // this is basically so Bun includes the file in the bundling process
...
new Worker(URL.createObjectUURL(Bun.file(workerTarget)));
...

worker-target.worker.ts

...
import { db } from "~/db/database";
...

all that works fine during dev (basically just bun run src/index.ts), and even builds fine, whether using

bun build --target bun --outdir ./dst src/index.ts

or

bun build --compile --target bun-linux-x64 --outfile dst/server src/index.ts

but when you try to run the built/bundled program either with

# inside dst directory, with node_modules directory present
bun run index.js

or

./server

I got an error Cannot find module '~/database' from 'blob:####' or something along those lines, which i guess makes sense because i guess worker files here are treated as an asset and the "reference" of the import is not solved.

And I feel like I am doing something very wrong, now the question is, is there any way or perhaps proper way to use Worker with build --compile or do i stuck just shipped the "raw source code" so the worker could function (because even doing bun build --target bun --outdir ./dst src/index.ts also doesn't work)