Just curious, why do the generated codes add the .ts extension to import/export statements?

[rxliuli]

For example

export { getBookmarks } from './clients/fetch/getBookmarks.ts'

This causes tsconfig to require adding "allowImportingTsExtensions": true, and at the same time, the noEmit or emitDeclarationOnly option must be added ¹, making it impossible to compile the code with tsc. I just want to know why the default value is like this?

---

In case anyone is interested, I used a command to batch replace all the generated files to solve this problem.

find src/kubb-client -name "*.ts" -type f -exec sed -i '' "s/from '\(.*\)\.ts'/from '\1'/g" {} \;

Footnotes

1. https://www.typescriptlang.org/tsconfig/#allowImportingTsExtensions ↩

[stijnvanhulle]

@rxliuli By default, we are adding .ts files as the latest Node.js version prefers adding an extension to every import.

A file extension must be provided when using the import keyword to resolve relative or absolute specifiers. Directory indexes (e.g. './startup/index.js' ) must also be fully specified. This behavior matches how import behaves in browser environments, assuming a typically configured server.

This could be overriden by using https://www.kubb.dev/getting-started/configure#output-extension, for example:

import { defineConfig } from '@kubb/core'

export default defineConfig({
  input: {
    path: './petStore.yaml',
  },
  output: {
    path: './src/gen',
    extension: {
      '.ts': '', // add empty comment to not use any extensions
    },
  },
})