Orval generates wrong import paths in ESM-only package

[jakubmazanec]

What are the steps to reproduce this issue?

Use custom Axios instance in ESM-only package (i.e. that uses type: "module" in package.json and "module": "node16", "moduleResolution": "node16" in tsconfig.json).

What happens?

Generated code that imports the custom Axios is:

import {customInstance} from './customInstance';

What were you expecting to happen?

Generated code that imports the custom Axios should be:

import {customInstance} from './customInstance.js';

Any logs, error output, etc?

TypeScript errors: Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './customInstance.js'? ​typescript(2835)

What versions are you using?

Package Version: 6.25.0

[melloware]

Hmmm i wonder if there is a way orval can detect what ts-config you are using? I somehow doubt it.

[jakubmazanec]

Maybe an option like useExtensionsInImportPaths: true would suffice? Anyway, extensions are mandatory when using ES modules, so it's not just TypeScript-related bug.

[melloware]

PR is welcome!