Inability to import .ts files to workflow or step files when using Nuxt

[mikkokut]

It is not possible to use shared typescript utility files in workflows / steps when using Nuxt.

When using relative imports, I see this error when navigating to app:

Unknown file extension ".ts" for /code/research/workflow-nuxt/server/utils/say.ts

When using import aliases such as import say from "@@/server/utils/say"; the build fails with error:

ERROR: Could not resolve "@@/server/utils/say"

Reproduction:
https://github.com/mikkokut/workflow-nuxt

Related to #261. I created a separate issue for Nuxt because there was a working workaround for Nitro.

[eersnington]

okay, the issue is a bit more deeper than I first thought it to be.

@pranaygp it looks like the decision to treat everything as external is deliberate swc-esbuild-plugin.ts-53-80. Isn't it better to make the builder treat every project local helper as part of the workflow bundle and only leave actual packages (node_modules or items the framework marks as external) outside?

2nd question: plans to feed framework aliases/tsconfig paths into the builder so @@/, ~/, etc resolve during bundling instead of crashing at runtime?

3rd (just got this idea from nextjs docs): should the workflow config expose a serverExternalPackages style option within the config? In nextjs, this lets you opt certain deps out of bundling when they rely on Node onyl APIs, while everything else stays bundled. Seems like the same mechanism would solve this bundling issue without losing control over platform specific packages

[eersnington]

I think @ijjk might be able to pick apart my thoughts better

[LindaJatique]

having the same problem here too

[pranaygp]

@adriandlam @atinux got any thoughts here? wondering if there's something we need to configure in workflow's internal esbuild usage to match compatibility with nuxt?

[pi0]

Nitro v3 (since alpha.1) natively supports tsconfig paths aliases.

In current nuxt versions, adding manual aliases is needed to nuxt.concig

[danielroe]

all nuxt aliases are exposed in our generated tsconfig.json files within the .nuxt folder, which are extended by the top level tsconfig.json in the user's directory. is it possible that workflow/esbuild isn't reading these?

[TooTallNate]

Is this still an issue or can this be closed?

[mikkokut]

Confirmed that works with beta.28. Thanks!