Clear and concise description of the problem

I believe exports.customExports should support an object as argument in addition to a function.

It feels a bit excessive to have to use a function to define one or two extra exports.

Suggested solution

import { defineConfig } from "tsdown";

export default defineConfig({
    entry: "./src/index.ts",
    copy: ["./src/binding/worker.wasm"],
    exports: {
        customExports: {
            "./worker.wasm": "./dist/worker.wasm",
        },
    },
});

Alternative

In my specific use-case it could also be possible to allow any files that were copied using copy to have exports generated.

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.