[BUG] custom defined tsconfig.node.json paths is not resolved on controler.

[kt-mabel]

Information

I am trying to implement a complex folder structure in ts.ed and it involves quite a few folders. In order to keep the imports section neat and easy to use I am trying to alias all important folder paths inside tsconfig.node.json.

Each path do get resolved on every single file except for Controllers. I always have to go with relative file path when it gets to controller imports.

Is there a solution to this problem?

I have defined custom path in tsconfig.node.json

Error:

• Version: cli-6.6.0,
  "@tsed/di": "^8.14.1",
  "@tsed/engines": "^8.14.1",
• Packages:

A few sentences describing the overall goals of the issue.

Example

Acceptance criteria

• Criteria 1

[Romakita]

Hum ok but you should look this problem with swc and typescript not with me ^^. Probably the swc configuration doesn't discover the paths set in tsconfig.

I use workspace (npm, yarn, pnpm) in combination with the ts paths, to be sure that the node module resolution are maintained by the package manager instead from the ts paths.

[kt-mabel]

@Romakita I tried a few thing. If swc was a problem then the problem would have been consistent throughout. It is only not working for Controllers. Any other file where I uses this custom ts paths is working. I thought I'll check with you if it is a know issue with ts.ed. Anyway I am debugging this issue, will raise another issue if it has something to do with ts.ed. Thanks. Closing it for now.

[github-actions]

🎉 Are you happy?

If you appreciated the support, know that it is free and is carried out on personal time ;)

A support, even a little bit makes a difference for me and continues to bring you answers!

[Romakita]

I never had this. I’ll try a test using cli.