Wrong (default) tsconfig.json used even though custom one is provided in tsup config

[mkosir]

I have my own tsconfig file path defined to be used for tsup

// tsup.config.ts
{
  entry: ['src/export-types/index.ts'],
  dts: { only: true },
  clean: true,
  tsconfig: 'tsconfig.build.json',
}

which has incremental: false

// tsconfig.build.json
{
  "compilerOptions": {
    ...
    "incremental": false,
    ...
}

Somehow tsup still pick up my (default) tsconfig.json, thats in the root of the project, which has "incremental": true and fails with an error:

CLI Building entry: src/export-types/index.ts
CLI Using tsconfig:tsconfig.build.json  <-- notice that tsup output in terminal states correct/defined tsconfig file
CLI tsup v6.5.0
CLI Using tsup config: tsup.config.ts
DTS Build start
error TS5074: Option '--incremental' can only be specified using tsconfig, emitting to single file or when option '--tsBuildInfoFile' is specified.

If I delete tsconfig.json in root folder (that of course must be present for VS code to pick it up, and for development config), tsup bundles with defined/correct tsconfig.build.json and no error.

[await-ovo]

It looks like rollup-plugin-dts will still load tsconfig.json even though tsup provides a way to customize the tsconfig path: https://github.com/Swatinem/rollup-plugin-dts/blob/master/src/program.ts#L38

[mkosir]

@await-ovo nice, thx for squashing this bug 🚀
iiuc for tsup this will be fixed when rollup-plugin-dts gets updated?

[await-ovo]

Yes, I think after the latest changes to rollup-plugin-dts are released, tsup only needs a little change and it should be fine ~

[github-actions]

🎉 This issue has been resolved in version 6.6.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀