runtimeConfigPath is copied verbatim instead of being resolved relative to generated output

[roiceee]

Description

Package: @hey-api/openapi-ts
Plugin: @hey-api/client-axios

Description

When using runtimeConfigPath with @hey-api/client-axios, the value is copied verbatim into the generated client files.

This causes incorrect imports unless the path is manually written relative to the generated output directory.

openapi-ts.config.ts:

import { defineConfig } from '@hey-api/openapi-ts';
import 'dotenv/config';

export default defineConfig([
  {
    input: `./schema1.json`,
    output: 'src/client/schema1',
    plugins: [
      '@hey-api/schemas',
      '@hey-api/sdk',
      '@hey-api/typescript',
      {
        name: '@hey-api/client-axios',
        runtimeConfigPath: './src/client/config/schema1.config.ts',
      },
    ],
  },
  {
    input: `./schema2.json`,
    output: 'src/client/schema2',
    plugins: [
      '@hey-api/schemas',
      '@hey-api/sdk',
      '@hey-api/typescript',
      {
        name: '@hey-api/client-axios',
        runtimeConfigPath: './src/client/config/schema2.config.ts',
      },
    ],
  },
]);

Generated Schema 1
import { createClientConfig } from './src/client/config/schema1.config.ts';

Generated Schema 2
import { createClientConfig } from './src/client/config/schema2.config.ts';

Reproducible example or configuration

https://stackblitz.com/edit/stackblitz-starters-z1bxoxgw?file=src%2Fclient%2Fschema1%2Fclient.gen.ts

OpenAPI specification (optional)

No response

System information (optional)

No response

[bolt-new-by-stackblitz]

Start a new pull request in StackBlitz Codeflow.

• stackblitz-starters-z1bxoxgw (Open reproduction)

[dosubot]

Hi @roiceee! I'm Dosu and I’m helping the openapi-ts team.

This looks like a valid bug. Based on the documentation, runtimeConfigPath is designed to let you provide a custom config file, but there's no explicit guidance on how path resolution should work.

The expected behavior would be for the path to be resolved relative to the generated output directory, so your config of './src/client/config/schema1.config.ts' with output src/client/schema1 should generate import { createClientConfig } from '../config/schema1.config.ts'; instead of copying the path verbatim.

Workaround: Until this is fixed, you can specify the path as it would appear relative to the generated file:

{
  name: '@hey-api/client-axios',
  runtimeConfigPath: '../config/schema1.config.ts',
}

This isn't ideal since it requires you to know the output directory structure, but it should produce correct imports.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}