Hi,
I recently started working with this library, having already implemented a couple of things with it before testing that it even works, since I didn't know until later about the job script detection system.
So far, it seems like everything mostly works right, except of course, the job script detection system. I turned on debug logs, and this is what I see, while running the nuxt dev server:
[12:41:57 PM] [debug] [2025-08-26 12:41:57] [Sidequest] [Job] : Resolving script file path. Stack lines: at buildPath (file:///home/bell/Projects/Homki/nuxt-dashboard/node_modules/@sidequest/core/dist/job/job.js:188:17)
at new Job (file:///home/bell/Projects/Homki/nuxt-dashboard/node_modules/@sidequest/core/dist/job/job.js:76:31)
at new UbiflowExportJob (file:///home/bell/Projects/Homki/nuxt-dashboard/.nuxt/dev/index.mjs:19208:5)
at JobBuilder.build (file:///home/bell/Projects/Homki/nuxt-dashboard/node_modules/@sidequest/engine/dist/job/job-builder.js:118:21)
at JobBuilder.enqueue (file:///home/bell/Projects/Homki/nuxt-dashboard/node_modules/@sidequest/engine/dist/job/job-builder.js:149:36)
at Object.handler (file:///home/bell/Projects/Homki/nuxt-dashboard/.nuxt/dev/index.mjs:19319:43)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async file:///home/bell/Projects/Homki/nuxt-dashboard/node_modules/h3/dist/index.mjs:2004:19
at async Object.callAsync (file:///home/bell/Projects/Homki/nuxt-dashboard/node_modules/unctx/dist/index.mjs:72:16)
at async Server.toNodeHandle (file:///home/bell/Projects/Homki/nuxt-dashboard/node_modules/h3/dist/index.mjs:2296:7)
The code for the job is on the 2nd line, but the issue is that it is not exported. So, Sidequest tries to fall back to the first line, which is just the base Job class, which is because, I assume, I call super() in the constructor.
Is there a simple way around this issue? I'd rather not go through the trouble of compiling TypeScript or hardcoding some paths...
Otherwise, this looks like an excellent library, really!
Hi,
I recently started working with this library, having already implemented a couple of things with it before testing that it even works, since I didn't know until later about the job script detection system.
So far, it seems like everything mostly works right, except of course, the job script detection system. I turned on debug logs, and this is what I see, while running the nuxt dev server:
The code for the job is on the 2nd line, but the issue is that it is not exported. So, Sidequest tries to fall back to the first line, which is just the base Job class, which is because, I assume, I call
super()in the constructor.Is there a simple way around this issue? I'd rather not go through the trouble of compiling TypeScript or hardcoding some paths...
Otherwise, this looks like an excellent library, really!