Imports with module: NodeNext

[ahmafi]

I'm using Orval 8.15.0 with module: NodeNext and moduleResolution: NodeNext in tsconfig.json. But still the imports don't have .js extensions. According to this #2284 it should be fixed. Am I missing something?

In tag-split mode none of the imports have extensions. For example in my index.ts I get this:

export * from "./dns/dns";

But should be:

export * from "./dns/dns.js";

My Orval config:

        input: "./openapi.yaml",
        output: {
            workspace: "./api/",
            target: "index.ts",
            namingConvention: "kebab-case",
            formatter: "biome",
            clean: true,
            client: "fetch",
            mode: "tags-split",
            headers: true,
            override: {
                mutator: {
                    path: "../custom-fetch.ts",
                    name: "customFetch",
                },
            },
        },

[melloware]

@rkday-pro you fixed this bug any ideas?

[ahmafi]

One more thing is that for my custom fetch to be imported correctly, I still have to define output.override.mutator.extention: '.js' to work. I think the default should also change for this, and the override should not be necessary.

[melloware]

@aqeelat thoughts??

[aqeelat]

@ahmafi @melloware issue identified. PR coming soon.

[aqeelat]

@ahmafi can you test against latest main?

[ahmafi]

@aqeelat Tested it. Looks good. Thanks again 👍