Typescript does not work with import alias

[nahtnam]

By default Next.js apps come with import alias of @/. I find that when using sidequest, it's failing when the file imports something like @/config

Is it possible to add a configuration option to invoke the job with tsx instead of node --experimental-strip-types?

[nahtnam]

Looks like it currently users worker threads under the hood? If tsx is enabled then can we just spawn a process? Less efficient but it will work

[GiovaniGuizzo]

Currently, there is no way of forcing tsx. We use worker threads as you rightfully noticed, thus it's a node process that's spawned. Apparently Node won't look at the tsconfig file, thus it does not know what to do when it sees a @/ import path.

Check this out: https://github.com/jonaskello/tsconfig-paths

Maybe that will solve your problem. You have to tell Node to use the paths specified in your tsconfig.

[nahtnam]

@GiovaniGuizzo Any examples by any chance?

I haven't been able to get it to work, including tsconfig-paths. I tried setting an env var NODE_OPTIONS="-r tsconfig-paths/register". The best I got is by getting vite to compile the typescript code and running it that way, however thats overall worse experience than bullmq.

I wonder if part of the issue is needing to pass execArgv options to the worker with the tsconfig-paths register too?

[GiovaniGuizzo]

Well, I don't know exactly. We've never encountered this issue before. Perhaps indeed we need to add this in the fork of the main worker. Does BullMQ allow TypeScript path alias?

[nahtnam]

I think bullmq does not use worker threads by default. So when I run tsx src/worker/start.ts, it just works as tsx handles the aliases for that process and the jobs run within that process

[GiovaniGuizzo]

I see. Then we have a limitation here. I will investigate how to include that lib in our main worker fork. This should fix the issue. Because we start a new fork process to run Sidequest in isolation, I suspect that if this fork uses that lib I mentioned, all the worker threads will have it by default.

I will have time next week to fix this.

[drewbaker]

@nahtnam take a look at my journey here #125

I suspect node sub-path imports is your answer