Upgrade to 0.9.4 lost all type safety?

[djMax]

I've upgraded from 0.8.2 to 0.9.4, tried both using the existing openapi-typescript generation as well as v7, but when I call create client with paths from the generator, it doesn't know about any methods/URL combinations - it runs fine, but typescript just doesn't have any idea what is going on. One concern is that I'm using CJS and wondering if maybe most people are not? Working on a repro, but I'm just very confused as to what is expected here - should 0.9.4 work with code generated by v6 openapi-typescript?

[djMax]

Here's a playground - it works in playground but not locally. I'm assuming it's a tsconfig issue.

Playground

{
  "include": [
    "@types/**/*",
    "src/**/*",
    "__tests__/**/*",
    "__mocks__/**/*",
    "coconfig.ts",
    "next-env.d.ts",
    "vitest.config.ts",
    "panda.config.ts",
    "tsup.config.ts"
  ],
  "exclude": [
    "node_modules",
    "dist"
  ],
  "ts-node": {
    "transpileOnly": true,
    "files": true
  },
  "compilerOptions": {
    "incremental": true,
    "lib": [
      "ES2022",
      "DOM"
    ],
    "target": "ES2022",
    "module": "NodeNext",
    "allowJs": true,
    "preserveWatchOutput": true,
    "outDir": "dist/",
    "strict": true,
    "declaration": true,
    "sourceMap": true,
    "isolatedModules": true,
    "moduleResolution": "NodeNext",
    "baseUrl": "./src",
    "allowSyntheticDefaultImports": true,
    "esModuleInterop": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "resolveJsonModule": true,
    "forceConsistentCasingInFileNames": true,
    "jsx": "react-jsx",
    "paths": {
      "@/*": [
        "./*"
      ]
    },
    "noEmit": true,
    "skipLibCheck": true
  }
}

[djMax]

Any of the three of these values breaks the module:

    // "target": "ES2022",
    // "module": "NodeNext",
    // "moduleResolution": "NodeNext",

[djMax]

The plot thickens - I think 0.9.3 is fine.

[djMax]

Referenced in #1635