Describe the feature

Currently, jiti does not support tsconfig.paths, which significantly impacts DX. This limitation exists to ensure that jiti remains portable and predictable by avoiding any reliance on external configuration files.

I’d like to propose adding a new option tsconfigPaths/tsconfigAliases which would be set to false by default. When enabled, jiti would resolve imports based on tsconfig.paths. This approach preserves the default behavior and predictability of jiti, while offering an opt-in improvement for those who want better DX in TypeScript projects.

The original comment where the proposal was discussed.

Additional information

• Would you be willing to help implement this feature?