Import aliases

[afonsomatos]

Import aliases

[samchon]

I may found a way to solve the problem. It is wrote on the #27

@afonsomatos and @hmmhmmhm, I'll try to solve this bug within 2 weeks. If you can't wait that time, you'd better not to use the alias feature of the tsconfig.json

[samchon]

@afonsomatos and @hmmhmmhm

Have fixed. Install the nestia v2.0 version and test it. All may be fine.

[samchon]

Looking at the new commit, there's no problem for the such alias imports.

To utilize the alias imports without error, run the nestia sdk command on a directory who've containing the tsconfig.json. Or run the nestia sdk command with newly configured nestia.config.json file with compilerOptions variable. I've prepared new examples for you. Read one of the below link, the you may understand how:

• tsconfig.json: https://github.com/samchon/nestia/tree/master/test/tsconfig.json
• nestia.config.json: https://github.com/samchon/nestia/tree/master/test/nestia.config.ts

[hmmhmmhm]

@samchon The same error occurs based on the latest nest. I cannot configure any form of absolute path. I specified it in tsconfig.json, and I specified it in nestia.config.ts, and it's the same.

[hmmhmmhm]

I provide you with a reproducible sample. nest operation works well, but if you type npx nestia sdk in your project, you will encounter problems.

• CodeSandbox: https://codesandbox.io/s/misty-grass-5jzu4w?file=/src/app.controller.ts
• Github: https://github.com/hmmhmmhm/nestia-issue-report-1

[samchon]

@afonsomatos, @hmmhmmhm

I'm sorry for such late update.

It was so difficult to fixing this bug, but from now on, any project would be failed by the alias paths.

It's the v2.0.8 update.