feature request: tsconfig alias path resolution

[asnaeb]

unplugin-typia version

0.6.18

What platform is your computer?

Darwin 23.5.0 arm64 arm

Describe the bug

When importing types from non relative paths, such types are parsed as any. Example of non relative paths are paths relative to tsconfig.compilerOptions.baseUrl or paths mapped from tsconfig.compilerOptions.paths.

Adding resolve.alias to vite.config.ts to map the paths in vite doesn't help.

Reproduction

https://github.com/asnaeb/vite-unplugin-typia-repro

run with npm run dev and check the console.

Validations

• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug.
• The provided reproduction is a minimal reproducible example of the bug.

[ryoppippi]

Thank you for reporting this.
Currently, I'm not implementing alias resolution.
Also, we don't implement for path resolution, so maybe typia compiler should implement it.

[ryoppippi]

I transfered this issue to typia's repo

[asnaeb]

Thank you for reporting this. Currently, I'm not implementing alias resolution. Also, we don't implement for path resolution, so maybe typia compiler should implement it.

I tested typia without the plugin and code transformed directly with typia generate works for both cases

[ryoppippi]

Oh, really. Could you give me an example?

[ryoppippi]

OK, so import {MyType} from "src/types/mytype"; is not appropriate for vite project. try use ./foo

[asnaeb]

Oh, really. Could you give me an example?

https://github.com/asnaeb/typia-test

• clone
• npm install
• npm run build
• inspect build directory

[ryoppippi]

I do not have time to do it, and actually I don't use alias so much, so your contribution are welcome
Maybe, you should contribute to mlly first.
unjs/mlly#271

[ryoppippi]

Also, typia compiler resolve import statement here
https://github.com/samchon/typia/blob/master/src/transformers/ImportTransformer.ts#L4
https://github.com/samchon/typia/blob/aeb14afc631c49009c00d9659ee36a3f8a01d2ca/src/programmers/TypiaProgrammer.ts#L67

[asnaeb]

I gave a quick look at it and seems like I've found a way to handle this without having to resolve anything from tsconfig but doing it the vite way: If non relative imports match something inside vite's resolve.alias, then imported types are resolved accordingly. I think this is the right way to handle this because it is exactly what one would expect. If you agree, I'm going to write some tests and submit a PR tomorrow.