Separate process worker not using TypeScript config

Created by: Enitoni

Description

I'm trying to import my modules in a separate process (using queue.process("path/to/processor.ts")) using TypeScript.

I get this error as soon as I try importing a module that is aliased using tsconfig-paths in the process file:

I need tsconfig-paths as it is what my entire application is using, is there a way to configure how the process is spawned, preferrably so I can set it to use my tsconfig.json?

Test code to reproduce

processor.ts import { something } from "aliased/modules"

Bull version

3.3.10