Migrate build tool from `tsup` to `tsdown`

[ognis1205]

Is there an existing issue or pull request for this?

• I have searched the existing issues and pull requests

Feature description

The project currently uses tsup as its build tool. However, tsdown is intended to replace tsup in the future and is actively positioned as its successor.

Desired solution

Migrate the project from tsup to tsdown following the official migration guide:

https://tsdown.dev/guide/migrate-from-tsup

Alternatives considered

• Continuing to use tsup until it is officially deprecated

Additional context

• build(npm): optimize tsup and tsconfig for node 18+ cli #1382 (comment)

[ognis1205]

If anyone would like to work on this, please feel free to take it on.

[mixator]

@ognis1205 I have created WIP pr for this one. I have found one CJS issue https://github.com/orhun/git-cliff/pull/1389/changes#diff-04e454d85cfc7abd09a68a1cd0f9c2fcbe83824de52ef9eb6d3e917cbd106863R19 and still working to resolve it

[ognis1205]

Hey @mixator , thanks for the effort!

I figured out the cause. I'll post a detailed comment later.

By the way, I noticed there are some things in the PR that shouldn't be included (maybe they're there to explain the build issue in the WIP). Just wanted to mention it.

[mixator]

@ognis1205
I'm planing to remove that code. Just wanna share my thoughts on it.

As I understand we could produce ESM only package since it cli tool and should not be used as programatic API. Is it right ?

[ognis1205]

@ognis1205 I'm planing to remove that code. Just wanna share my thoughts on it.

As I understand we could produce ESM only package since it cli tool and should not be used as programatic API. Is it right ?

Sorry for the late reply.

While the CLI is the primary concern for most users, we do officially provide a programmatic API as described here:

https://git-cliff.org/docs/installation/npm

Given that, I think we should continue supporting CLI usage as well as both ESM and CJS builds.

Regarding the CJS build error, that issue is completely orthogonal to the tsup -> tsdown migration. Please feel free to open a separate issue or PR for it. If opening an issue feels like overhead, I'm happy to take care of it myself.

For now, it's totally fine for the migration PR to focus strictly on the migration itself, since the CJS issue is unrelated.